1. Questions & ad-hoc Documentation
1.1. Questions from Grooming with Beer Friday
1.2. Five Steps to SEO-Friendly Site URL Structure
1.2.1. How do we Plan on Handling this: SEO-wise, not all URLs on a site are of equal importance as a rule. Some even should be concealed from the search engines. At the same time, it is important to check that the pages that ought to be accessible to the search engines are actually open for crawling and indexing.
1.2.2. How do we plan to consolidate www and non-www domain versions? 1. 301 2. Google Webmaster Tools 3. Canonicals
1.2.2.1. 301 Most SEOs (in my experience) use the 301 redirect to point one version of their site to the other (or vice versa).
1.2.2.2. Google Webmaster Tools Specify your preferred version i in Configuration >> Settings >> Preferred Domain ----- Drawbacks: 1. This takes care of Google only 2. This option is restricted to root domains only. If you have an example.wordpress.com site, this method is not for you
1.2.2.3. WHY worry about the www vs non-www issue in the first place? Thing is, some of your backlinks may be pointing to your www version, while some could be going to the non-www version
1.3. FAQs
1.3.1. How do I find a Business defined Tier 2 Site?
1.3.1.1. Based on the Business definition, a Tier 2 site = Group Site
1.3.1.2. DNA > Client Search > 'Asbury' > Select accountid 'asbury' > Open the 'Groups' Tab > Sites listed below top account id are Tier 2 Sites
1.3.1.3. Once you have accessed a Tier 2 site in a browser > View Page Source > Look for similar: newrelic.setCustomAttribute('pageId','asburyprofile_V2_INDEX_GROUP');
1.3.2. I see Inventory in the Sitemap, but it's not on the site
1.3.2.1. Site could be using a Sticky Make or an Exclude Make
1.3.2.2. Check to see that the Make is listed in the franchise tags inside the config.xml for the site
1.3.2.3. Are you looking at a set of search results based on: (see below) Similar URL paths ----- /new-inventory/index.htm /used-inventory/index.htm /certified-inventory/index.htm You should change your search to look via: (see below) /all-inventory/index.htm
1.3.3. SEO URL Feature has been turned on , in DNA, I don't see SEO URLs in the sitemap yet
1.3.3.1. Check SOLR for Inventory
1.3.3.2. Check your Inventory Setup
1.3.4. SEO Link Checker
1.3.5. Why do we need the trailing slash on the SEO Friendly URL?
1.3.5.1. Regarding the trailing slash, this is an artifact of our Tomcat configuration, and the way Tomcat works. Because the DefaultServlet is the default servlet, it handles all requests not explicitly mapped to specific servlets. The trailing slash causes the request to be mapped to the main Controller. The main Controller could be made the default servlet, but then it would have to be able to safely handle any type of un-mapped request AND we would need to explicitly map all of the static assets to the DefaultServlet that we need to serve out of cms-web (which I'm not sure we can do without colliding with mappings required by other servlets).
1.4. Composite Inventory Type
1.4.1. @HarithaYalamanchili ran into a composite type in my testingThese three links are in the sitemap (SEO turned on)http://cogginbmwtreasurecoast.cms.dev.dealer.com/inventory/used/Mercedes--Benz-GLK/ http://cogginbmwtreasurecoast.cms.dev.dealer.com/inventory/certified-preowned/Mercedes--Benz-GLK/ http://cogginbmwtreasurecoast.cms.dev.dealer.com/inventory/used/Mercedes--Benz-GLK--Class/Click those links to see that you reach a no inventory page------ Contrast: Went into the site > Searched Used > Set Condition = Certified > Make = Mercedes Benz > Model = GLKThis Search Results in 2 Certified vehicles http://cogginbmwtreasurecoast.cms.dev.dealer.com/used-inventory/index.htm?listingConfigId=auto-used&...---- Contrast: Went into the site > Searched Used > Make = Mercedes Benz > Model = GLK **Did not set the ConditionThis search results in 3 Used Vehicles http://cogginbmwtreasurecoast.cms.dev.dealer.com/used-inventory/index.htm?listingConfigId=auto-used&...--- Lastly - Contrast: Went into the site > Searched Used > Make = Mercedes Benz > Model = GLK-Class **Did not set the ConditionThis search results in 1 Used Vehicle http://cogginbmwtreasurecoast.cms.dev.dealer.com/used-inventory/index.htm?listingConfigId=auto-used&...
1.5. Google Recommendations
1.5.1. 301 and Canonical are 95% similar in how they are ranked by Google - Matt Cutts
1.5.2. Google recommends using hyphens (-) instead of underscores (_) in URLs
1.6. SEO Cheat Sheet
1.7. Structured Data Testing Tool
2. US56682: Update "canonical ref"s for existing VLP pages to reveal SEO friendly values
2.1. Description
2.1.1. As a developer we need to review all flavors of VLP pages to determine if canonical ref needs to be refactored
2.2. Acceptance Criteria
2.2.1. Verify DR/Non DR VLP pages for V9 for correct implementation of canonical html tag for SEO non friendly URL's (existing VLP) where SEOURL feature is enabled for the site
2.2.2. Verify canonical reference is correct for inventory/New
2.2.3. Verify canonical reference is correct for inventory/Used
2.2.4. Verify canonical reference is correct for inventory/Certified
2.2.5. 'Pagestack' needs to be vetted against Automated Regression
2.3. Testing Approach
2.3.1. Canonical
2.3.1.1. For SEO Friendly URL Variations **Defined in US51198
2.3.1.1.1. For Inventory Type Variations **Defined in US51198
2.3.1.2. General Expectations
2.3.1.2.1. Canonical Logic Scenarios play-out as detailed
2.3.2. Pagestack
2.3.2.1. Full Automated Regression
2.3.2.1.1. Composer
2.3.2.1.2. cms-web
2.3.2.1.3. Re-run Prior Tests Van has created
2.3.3. Automation
2.3.3.1. Canonicals
2.3.3.1.1. Expanded for the Canonical Logic being applied
2.3.3.2. String Combos
2.3.3.2.1. Top Level sets of combos to limit test runtime
2.4. Canonical Logic
2.4.1. Make(n)
2.4.1.1. Results in
2.4.1.1.1. Old-Style URL
2.4.2. Make(1)
2.4.2.1. Results in
2.4.2.1.1. Make
2.4.2.1.2. SEO URL
2.4.3. Make(1) + Model(1)
2.4.3.1. Results in
2.4.3.1.1. Make + Model
2.4.3.1.2. SEO URL
2.4.4. Make(1) + Model(n)
2.4.4.1. Results in
2.4.4.1.1. Old-Style URL
2.4.5. Make(0) + Model(1) || Make(n)
2.4.5.1. Results in
2.4.5.1.1. Old-Style URL
2.5. Pagestack
2.5.1. What is it doing
2.5.1.1. Page Alias from Sitemap (From DVS)
2.5.1.1.1. Site Proxy First, Variation Second, Default last
2.5.2. Where does it affect
2.5.2.1. SaveNavigation
2.5.2.1.1. Homepage
3. US4837: DNA Set up
3.1. DNA
3.1.1. DNA > Client > Features > SmartSites.SEOURLs
3.1.1.1. Look for the Feature in the listing
3.1.1.2. Default state: Should be OFF
3.1.1.3. User can turn ON the Feature
3.1.1.4. User can turn OFF the Feautre
3.1.1.5. ON/OFF state is saved and can be retrieved
3.1.1.6. When ON/OFF is set for any Client/Account > It does not affect the state of another
3.1.2. Groups
3.1.2.1. DNS Group As Seen in the DB
3.1.2.1.1. Users in these Groups will see the Feature in the Configurable Resources Section of the DNA Features
3.1.2.1.2. Users in this Group will be able to turn the Feature ON/OFF
3.1.2.1.3. Users NOT in these Groups will see the Feature in the Non-Configurable Resources Section of the DNA Features
3.1.2.1.4. Users NOT in this Group will NOT be able to turn the Feature ON/OFF
3.2. DB
3.2.1. Nexus > resource.name
3.2.1.1. Look for "SmartSites.SEOURLs"
3.2.1.2. **Dev Table replication takes about 20 minutes
3.2.2. Nexus > resource_group_map
3.2.2.1. resource_name
3.2.2.2. dna_group
3.2.2.3. Access Level
3.3. Unit Test
3.3.1. Wrapper in Velocity
3.3.1.1. @Test public void shouldBeMissingResource() { assertFalse(helper.checkDNAResource("", "bluesteeldemo5")); }
3.3.1.2. ***This will fail until the resource has been added
3.4. **Terminology
3.4.1. DNA > Feature
3.4.2. DB > Resource
4. US47506: Enhance inventory URL interceptor
4.1. Description
4.1.1. No Basic Description was recorded
4.2. Acceptance Criteria
4.2.1. Route new inventory requests to VLP
4.2.2. Verify for 404 before change, but new url routes are working after the change
4.2.2.1. new (no geo marketing)
4.2.2.2. Old: /inventory/new/{model}/index.htm
4.2.2.3. New: https://ddcdemohonda.financing.localhost.dealer.com/inventory/new/Honda-Accord/ https://bluesteel.cms.localhost.dealer.com/inventory/new/Acura-MDX/ https://bluesteel.cms.localhost.dealer.com/inventory/used/Scion/ https://bluesteel.cms.localhost.dealer.com/inventory/certified-preowned/Jaguar/
4.3. Basic Testing Approach
4.3.1. Compare Inventory and Vehicle Count
4.3.1.1. SEO URL Inventory results
4.3.1.2. Search via Site tools
4.3.1.2.1. Smart Search
4.3.1.2.2. VLP > Facet selection
4.3.2. Vehicle Selection
4.3.2.1. 10-20 - Makes & Models
4.3.2.1.1. New
4.3.2.1.2. Used
4.3.2.1.3. Certified / Pre-owned
4.3.3. Site Selection
4.3.3.1. http://beerfridayautotest.cms.dev.dealer.com/
4.3.3.2. http://beerfriday.cms.dev.dealer.com/
4.3.3.3. https://spectredemo.cms.dev.dealer.com
4.3.3.4. https://bluesteel.cms.dev.dealer.com
4.3.3.5. https://unikitty.cms.dev.dealer.com
4.3.3.6. https://ddcdemohonda.cms.dev.dealer.com
4.3.3.7. 100 Sites
4.3.4. rewrite-status Rules
4.3.4.1. Look for the 'SEO Inventory Rule'
4.3.4.1.1. https://bluesteel.cms.dealer.com/rewrite-status
4.3.4.1.2. URL's matching ^/inventory/(new|used|certified-preowned)/(.*)/$ will be forwarded to %{attribute:standardVLPUrl}. This rule and it's conditions will use the regex matching engine. This rule will run: setVehicleSeoUrl(javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse) on an instance of com.dealer.cms.web.filters.urlrewrite.VehicleSeoUrlHelper Note, if init(ServletConfig) or destroy() is found on the above object they will be run at when creating or destroying an instance. Note, other rules will be processed after this rule.
5. Feature Overview & Context
5.1. SEO Analyst > DESIRES > VLPs with unique URLs > Make/Model/Trim > TO AVOID > Custom VLP work & > IMPROVE > Model Specific Search result ranking
5.2. VLP URLs are not SEO Friendly > DUE TO > No static page for Make/Model/Trim >
5.2.1. PREVENTS > Customization of Make/Model/Trim VLP
5.2.2. Ranking Loss > TO > inventory aggregators & competitor’s websites
5.2.3. CAUSES > Creation of Custom VLPs > Which don’t function w/VLP facet browse system > CAUSES > Negative UEx
6. Benefits
6.1. As a SEO subscriber, this feature allows my website to see increased rankings for keywords related to the makes & models that I currently have on my lot. Increased organic traffic leads to more conversions & ultimately, higher sales, better profits & increased ROI.
6.2. As an SEO Analyst, this feature eliminates the time I need to spend manually building custom VLP pages so that I can use that time for fixed ops & other SEO tactics that will allow me to show enhanced results for the SEO program.
7. Measurement of Success
7.1. SEO client websites seeing an increase in organic visibility for make/model/trim related keywords - measured with AWR Cloud (already set up to measure this when complete)
7.2. Increased sales of SEO services
7.3. Reduced churn of SEO subscribers
8. In-Scope
8.1. feature needs to be tied to a Dealer.com SEO service subscription
8.2. T11 & it’s variations
8.3. Available for use on all OEM sites (again, SEO subscribers only but available for OEM programs) - ensure Compliance w/ Eileen
8.4. URL Structure Priority 1
8.5. New Only for Phase 1
9. SME's
9.1. Kieth Porter
9.2. Matt Turnbull
9.3. Pete Bruhn
9.4. Chris Nichols
10. Stakeholders
10.1. Pete Bruhn
10.2. Chris Nichols
10.3. Dan Durick
10.4. Scott Blodget
10.5. Zach Clayton
11. US52908: Update "canonical ref"s for new virtual URL paths
11.1. Description
11.1.1. As a developer we need to review all flavors of VLP pages to determine if canonical ref needs to be refactored.
11.2. Acceptance Criteria
11.2.1. Verify DR/Non DR VLP pages for V9 for correct implementation of canonical html tag for SEO non friendly URL's (existing VLP)
11.2.2. Verify DR/Non DR VLP pages for V9 for correct implementation of canonical html tag for SEO friendly URL's (new VLP paths)
11.2.3. Verify canonical reference is correct for inventory/New
11.2.4. Verify canonical reference is correct for inventory/Used
11.2.5. Verify canonical reference is correct for inventory/Certified
11.3. Examples:
11.3.1. VLP (old style)
11.3.1.1. URL
11.3.1.1.1. /new-inventory/index.htm?search=&make=Acura&model=MDX
11.3.1.2. Canonical
11.3.1.2.1. /new-inventory/index.htm
11.3.2. VLP (new style): /inventory/new/Acura-MDX/
11.3.2.1. URL
11.3.2.1.1. /inventory/new/Acura-MDX/
11.3.2.2. Canonical
11.3.2.2.1. /inventory/new/ACURA-MDX/
11.3.3. This tag should be used in your header information to indicate that if there are duplicate pages on your website, you want Google to know which is the right page.
11.3.3.1. SEO Friendly URL takes the consumer to New/Acuras
11.3.3.1.1. canonical should follow the pattern of the new style (example above)
11.3.3.2. Inventory Listing + Listing=New + Filter = 'Acura' takes the consumer to the same as the SEO Friendly URL
11.3.3.2.1. canonical should follow the pattern of the old style (example above)
11.4. https SEO Friendly URL on a site configured for SSL
11.4.1. Page URL: https://lithiatoyotascionofgrandforks.cms.dev.dealer.com/inventory/used/Dodge/
11.4.1.1. <link rel="canonical" href="https://www.toyotaofgrandforks.com/inventory/used/Dodge/" />
11.4.1.2. SEO Friendly URL: https://lithiatoyotascionofgrandforks.cms.dev.dealer.com/inventory/used/Dodge/
11.5. http SEO Friendly URL on a Site configured for SSL
11.5.1. Page URL: https://lithiatoyotascionofgrandforks.cms.dev.dealer.com/used-inventory/index.htm?make=Dodge
11.5.1.1. <link rel="canonical" href="https://www.toyotaofgrandforks.com/used-inventory/index.htm">
11.5.1.2. SEO Friendly URL: http://lithiatoyotascionofgrandforks.cms.dev.dealer.com/inventory/used/Dodge/
11.6. Testing Approach
11.6.1. Flow
11.6.1.1. Step 1: Go into DNA > Turn on SEO Feature for the associated account
11.6.1.2. Step 2: Open Web page > View Source > Search for 'canonical'
11.6.1.2.1. Pages that match the SEO Friendly URL
11.6.1.2.2. Pages that use the virtual path
11.6.1.3. Step 3: Go into DNA > Turn off SEO Feature for the associated account
11.6.1.3.1. Repeat Step 2
11.6.2. http://kiadmggroupnewyork.cms.dev.dealer.com
11.6.2.1. Ignore
11.6.3. Inventory Types
11.6.3.1. New
11.6.3.2. Used
11.6.3.3. Certified-Preowned
11.6.4. Sites
11.6.4.1. 9.2
11.6.4.1.1. 9.2 Specific OEMs
11.6.4.1.2. Parent 0001 Theme
11.6.4.2. Asbury
11.6.4.2.1. DR enabled sites
11.6.4.2.2. Non-DR enabled sites
11.6.4.3. International/Languages
11.6.4.3.1. English US > ?locale=en_US
11.6.4.3.2. Spanish US > ?locale=es_US
11.6.4.3.3. English Canadian > ?locale=en_CA
11.6.4.3.4. French Canadian > ?locale=fr_CA
11.6.4.3.5. Spanish Mexico > ?locale=es_MX
11.6.4.4. NPV Inventory type
11.6.4.4.1. NPV - Non-Passenger Vehicle
11.6.4.4.2. http://stongetc.cms.dev.dealer.com/sitemap.xml
11.6.4.5. Group 1
11.6.4.5.1. v9_CLIENT_GROUPONE_0004_V1
12. US51198: Refactor: support pagination navigation & seo encoding/decoding
12.1. Description
12.1.1. Currently the virtual path forwarding does not support passing existing query string values along to the destination path. This breaks existing functionality on VLP pages on next/previous navigation buttons.
12.2. Acceptance Criteria
12.2.1. Allow Pagination to work for SEO friendly URL's by allowing query strings in the url rewrite and passing the query strings along to the destination path
12.2.2. Verify in the case of colliding parameters query string parameters win
12.2.3. Update any SEO encoding/decodings:
12.2.3.1. Space
12.2.3.1.1. Encoding
12.2.3.1.2. Decoding
12.2.3.2. Ampersand
12.2.3.2.1. Encoding
12.2.3.2.2. Decoding
12.2.3.3. Hyphen/ Dash
12.2.3.3.1. Encoding
12.2.3.3.2. Decoding
12.2.3.4. Solidus/ Forward Slash
12.2.3.4.1. Encoding
12.2.3.4.2. Decoding
12.2.3.5. All other special characters will be need to be identified in order to work out an encoding schema
12.3. SEO encoding/decodings:
12.3.1. Encoding
12.3.1.1. Space
12.3.1.1.1. Encoding
12.3.1.1.2. Decoding
12.3.1.2. Hyphen/ Dash
12.3.1.2.1. Encoding
12.3.1.2.2. Decoding
12.3.1.3. Ampersand
12.3.1.3.1. Encoding
12.3.1.3.2. Decoding
12.3.1.4. Solidus/ Forward Slash
12.3.1.4.1. Encoding
12.3.1.4.2. Decoding
12.3.1.5. All other special characters will be need to be identified in order to work out an encoding schema
12.3.2. Decoding
12.3.2.1. Special characters will be uri encoded as fall thru (e.g. decoded similar to “/“ = %2F) - Using an UTF-8 Character set for Phase 1 areas affected
12.3.2.1.1. http://www.w3schools.com/charsets/ref_utf_basic_latin.asp
12.4. Inventory Type URL Variations
12.4.1. New
12.4.1.1. .../inventory/new/...
12.4.2. Used
12.4.2.1. .../inventory/used/....
12.4.3. Certified-preowned
12.4.3.1. .../inventory/certified-preowned/...
12.5. URL Variations
12.5.1. SEO Friendly URL
12.5.1.1. Contains URL elements and Parameters
12.5.1.1.1. Make
12.5.1.1.2. Model
12.5.1.1.3. Make+Model
12.5.1.1.4. For SEO Friendly URL Variations of Make, Model, and Make+Model
12.5.2. Old-Style URL
12.5.2.1. Contains Parameters
12.5.2.1.1. Params include Make
12.5.2.1.2. Params include Model
12.5.2.1.3. Non Make and/or Model Params
12.6. Parameter Variations
12.6.1. Make
12.6.1.1. Only 1 Parameter
12.6.1.1.1. Make Parameter
12.6.1.1.2. Parameter with No Value
12.6.1.2. More than 1 Parameter
12.6.1.2.1. Same Value
12.6.1.2.2. Different Values
12.6.1.2.3. Parameters with No Value
12.6.2. Model
12.6.2.1. Only 1 Parameter
12.6.2.1.1. Model Parameter
12.6.2.1.2. Parameters with No Value
12.6.2.2. More than 1 Parameter
12.6.2.2.1. Same Value
12.6.2.2.2. Different Value
12.6.2.2.3. Parameters with No Value
12.6.3. Make + Model
12.6.3.1. Only 1 Parameter each
12.6.3.1.1. Model Parameter
12.6.3.1.2. Make Parameter
12.6.3.1.3. Parameters with No Value
12.6.3.2. 1 Make and More than one Model Parameters
12.6.3.2.1. Same Model Parameters
12.6.3.2.2. Different Model Parameters
12.6.3.2.3. Parameters with No Value
12.6.3.3. 1 Model and More than one Make Parameters
12.6.3.3.1. Same Make Parameters
12.6.3.3.2. Different Make Parameters
12.6.3.3.3. Parameters with No Value
12.6.3.4. More than one Make and Model Parameters
12.6.3.4.1. Same Model Parameters
12.6.3.4.2. Same Make Parameters
12.6.3.4.3. Different Model Parameters
12.6.3.4.4. Different Make Parameters
12.6.3.4.5. Parameters with No Value
12.6.4. Additional Params
12.6.4.1. Accounting for Make, Model, & Make + Model Parameter scenarios
12.6.4.1.1. Additional parameters
12.7. Example URLs
12.7.1. https://bluesteel.cms.localhost.dealer.com/inventory/new/Acura/?make=Toyota&make=Toyota&model=MDX
12.7.2. https://bluesteel.cms.localhost.dealer.com/inventory/new/Acura/?model=MDX
12.7.3. https://bluesteel.cms.localhost.dealer.com/inventory/new/Toyota/?model=Avalon
12.7.4. https://bluesteel.cms.localhost.dealer.com/inventory/new/Toyota/?model=Avalon&model=Camry
12.7.5. https://bluesteel.cms.localhost.dealer.com/inventory/new/Toyota/
12.7.6. https://bluesteel.cms.localhost.dealer.com/inventory/new/Acura/
12.7.7. https://bluesteel.cms.localhost.dealer.com/inventory/new/Acura/?color=blue
12.7.8. https://bluesteel.cms.localhost.dealer.com/inventory/new/Toyota-Avalon/?model=Camry
12.7.9. https://bluesteel.cms.localhost.dealer.com/inventory/new/Toyota-Camry/?model=Avalon
12.7.10. Get additional URLS to test with
12.7.10.1. Get Virtual Path from an Inventory Search
12.7.10.1.1. Edit URL to be SEO Friendly
12.8. Facet Selection Configuration
12.8.1. Multi-facet selection allowed on VLP
12.8.2. ONLY Single Facet selection allowed on VLP
13. US62199: Ignore Params to Build Canonical URL
13.1. Description
13.1.1. The params passed in the URL should always be ignored while building the canonical URLs whether they are SEO or non SEO URLs
13.2. Acceptance Criteria
13.2.1. Canonical should be an SEO friendly URL
13.2.2. Verify New URL with params Eg: .../inventory/new/<Make1>-<Model1>/?param<Make1>&<Model1>
13.2.3. Verify New URL with params Eg: .../inventory/new/<Make1>-<Model1>/?param<Make2>&<Model2>
13.2.4. Verify old URL with params Eg: .../new-inventory/index.htm?make=Toyota&?model=Tacoma
13.2.5. Verify New URLwith no params Eg: .../inventory/new/<Make>-<Model>/
13.3. Testing Approach
13.3.1. Retry known URLs
13.3.1.1. Watch for changes in behavior
13.3.2. Watch Canonical
13.3.2.1. Compare with Expectations
13.3.3. Include Logic from prior Tested Stories
13.4. Testing Results
13.4.1. Cynthia:
13.4.1.1. US58664
13.4.1.2. US56682
13.4.1.3. US51198
13.4.1.4. US52908
13.4.2. Chris:
13.4.2.1. US59398
13.4.2.2. US58935
13.4.3. Van:
13.4.3.1. Automation Scripts for F6798
14. US59398 & US58935: V2 & V1 Desktop and Mobile
14.1. Description
14.1.1. As a developer we need to change window.location to load new SEO friendly page when 1 make or 1 model is selected
14.2. Acceptance Criteria
14.2.1. When one make or one model is selected, use new SEO friendly URL
14.2.2. When more than one make or model is selected, use the old style URL
14.2.2.1. US59398: Test V2 inventory listing widget only
14.2.3. When a facet is removed, leaving a single make or model, use new SEO friendly URL
14.2.4. Test for mobile
14.2.5. Test inventory listing widget
14.2.5.1. US59398: Test V2 inventory listing widget only
14.2.5.2. US58935: Test V1 inventory listing widget only
14.3. Testing Approach
14.3.1. V2
14.3.1.1. Employ the Facets
14.3.1.1.1. When Make and/or Make + Model selections are unique
14.3.1.1.2. When Make and/or Make + Model selections are not unique
14.3.1.1.3. Additional Facet selections
14.3.2. V1
14.4. Testing Results
14.5. Original Story
14.5.1. US56684: Clicking model / make checkbox facets on facet search page should use new seo friendly url
14.5.2. Acceptance Criteria
14.5.2.1. When one make or one model is selected, use new seo friendly url
14.5.2.2. When more than one make or model is selected, use the old style url
14.5.2.3. When a facet is removed, leaving a single make or model, use new seo friendly url
14.5.2.4. Include BMW CPO in the test plan
15. US59396: Sitemap.xml filter on Sticky/Exclude Make & Model DNA settings
15.1. Description
15.1.1. As a webcrawler, I have the ability to find specific makes and models in the sitemap.xml based on the SOLR inventory and the specific DNA settings per account based on the specific listing config id.
15.1.2. As a Production user, I can configure a dealer site to exclude specific make/models or include specific make/models. These settings should be respected in the sitemap.xml entry generation.
15.2. Acceptance Criteria
15.2.1. Make(s) and Model(s) defined in Exclude Makes, Exclude Models, Sticky Makes, and Sticky Models should further filter the contents in sitemap xml entry generation. This is specific to listing config id.
15.2.1.1. Verify Hide Certified
15.2.1.2. Verify Sticky Makes
15.2.1.3. Verify Sticky Models
15.2.1.4. Verify Exclude Makes
15.2.1.5. Verify Exclude Models
15.3. Testing Approach
15.3.1. Apply the Logic pathways + Combine attribiutes
15.3.1.1. Observe the Outcome on the sitemap
15.3.2. Logic
15.3.2.1. Inventory Category
15.3.2.1.1. Listing Config ID
15.3.2.2. for Category: Categories
15.3.2.2.1. Get ConfigurationsByCategory
15.3.2.3. config.xml
15.3.2.3.1. Franchises
15.4. Testing Results
15.4.1. Additional Testing Results
15.5. Need to know the Category of the inventory
15.5.1. SOLR Query: http://vtdevwebsol-solrautoslave10.dealer.ddc:9650/solr-inventory/#/inventory/query q uuid: <uuid> - replace with value for the piece of inventory wt json indent
15.5.1.1. Example UUID uuid: 802e66170a0a000201e33bb855baee1c
15.5.1.2. Example SOLR output category":"ATV"
15.6. Need to know the Inv. Config for an Account
15.6.1. DNA > From the Client Dashboard <Account>
15.6.1.1. Inv. Config
15.6.1.1.1. Select From Existing or Default Listing IDs > Click 'Search' > Classes
15.7. Need to know the franchises that are specified for the site
15.7.1. http://dvs.dev.dealer.ddc/rest/configs/<account>/config
15.7.1.1. <franchises>...</franchises> can be seen here
15.7.1.1.1. stongetc
15.7.1.1.2. bluesteel
15.8. SolrException
15.8.1. Causes the Sitemap to not generate SEO URLs
15.8.1.1. SOLUTION
16. US49011: Integrate inventory into Sitemap servlet for New, Used, and Certified-Preowned
16.1. Description
16.1.1. No Basic Description was recorded
16.2. Acceptance Criteria
16.2.1. Sitemap.xml to display permutations of make, model for new, used, and certified-preowned vehicles
16.2.2. Verify Tier 2 sites
16.2.2.1. Technically defined Tier 2 Sites
16.2.2.2. Business defined Tier 2 Sites
16.2.3. Verify Non Tier 2 Sites
16.2.4. Verify truncation for >50 MB data
16.2.5. Verify truncation for record generation for over 50,000 records
16.3. SCOPE
16.3.1. All Sites
16.3.2. V8 - This was not excluded from V8 Sites
16.4. Testing Approach
16.4.1. Sites:
16.4.1.1. Hard-coded Tier 2 Sites:
16.4.1.1.1. audioffers
16.4.1.2. Group Site: mcdavid
16.4.1.3. Non Tier 2 Sites
16.4.1.3.1. bluesteel
16.4.1.3.2. spectredemo
16.4.1.4. Limiting Factor Sites
16.4.1.4.1. <acquire a dev URL> Contact outside the team for an example site
16.4.2. For identified Sites > Add sitemap.xml/ to the end of the URL
16.4.2.1. For Each type of Inventory
16.4.2.1.1. Verify that the output appears to be formed correctly
16.4.2.1.2. Verify the Make links match a selection of the Site Inventory
16.4.2.1.3. Verify the Make + Model links match a selection of the Site Inventory
16.4.3. Sitemap
16.4.3.1. Verify On state
16.4.3.2. Verify Off state
16.4.4. Inventory
16.4.4.1. Parent Child Relationship
16.4.4.1.1. Parent and/or Child have their own SOLR Inventory
16.4.4.1.2. Child does not have its own SOLR Inventory
16.4.4.2. Types
16.4.4.2.1. AUTO
16.4.4.2.2. REALESTATE_CA
16.4.4.2.3. COMMERCIAL_CA
16.4.4.2.4. LAND_CA
16.4.4.3. DNA > ACCOUNT > INV. CONFIG > Listing IDs
16.4.4.3.1. NEW
16.4.4.3.2. USED
16.4.4.3.3. ALL
16.4.4.3.4. <user-defined>
17. US58664: Extend meta data which are title, descriptions and key words like it was done in canonical
17.1. Description
17.1.1. When a car shopper visits an inventory listings page that is an SEO friendly URL, the meta data on that page should include the make & model information of that page.
17.2. Acceptance Criteria
17.2.1. SEO Meta Data should override existing Meta Data already configured in Composer (DVS MetaData). SEO tags <make> & <model> are specially handled during the SEO Interceptor process
17.2.2. Verify meta data in English, French and Spanish
17.2.3. Verify meta data for title, description, keywords, og title, og description
17.3. Testing Approach
17.3.1. Automation has been expanded to look for the resulting metadata
17.3.1.1. Listing Config IDs
17.3.1.1.1. new used certified-used
17.3.1.2. Locales
17.3.1.2.1. en_US en_CA fr_CA es_US es_MX
17.3.1.3. Meta Data
17.3.1.3.1. <title>{content}</title>
17.3.1.3.2. <meta name="description" content={content}/>
17.3.1.3.3. <meta name="keywords" content={content}/>
17.3.1.4. og title
17.3.2. Manual Testing covered the cases defined in this Google Sheet
17.4. Testing Results
18. US60874: Release SEO
18.1. US47506
18.1.1. Enhance inventory URL interceptor
18.1.2. Check for the rewrite status Rule
18.2. US49011
18.2.1. Integrate inventory into Sitemap servlet for New, Used, and Certified-Preowned
18.2.2. Automation Tests are covering this
18.3. US52908
18.3.1. Update "canonical ref"s for new virtual URL paths
18.3.2. Automation Tests are covering this
18.4. US51198
18.4.1. Refactor: support pagination navigation & seo encoding/decoding
18.4.2. Automation Tests are covering this
18.5. US56682
18.5.1. Update "canonical ref"s for existing VLP pages to reveal SEO friendly values
18.5.2. Automation Tests are covering this
18.5.3. US62199
18.5.3.1. Ignore Params to Build Canonical URL
18.5.3.2. Automation Tests are covering this
18.6. US58664
18.6.1. Extend meta data which are title, descriptions and key words like it was done in canonical
18.6.2. Automation Tests are covering this
18.7. US59396
18.7.1. Sitemap.xml filter on Sticky/Exclude Make & Model DNA settings
18.7.2. 1
18.7.2.1. DNA Constraints to Site map: Hide Certified Tiurned on
18.7.2.1.1. DNA > Account: bluesteel > Features: SmartSites.SEOURLs is enabled > Inv. Config > Inventory Listing ID = used > Class = Primary > Class Category = Used > Exclude Certified is enabled https://bluesteel.cms.<environment>.dealer.com/sitemap.xml
18.7.3. 2
18.7.3.1. DNA Constraints to Site map: Sticky Makes and/or Models specified
18.7.3.1.1. For Make
18.7.3.1.2. For Model
18.7.4. 3
18.7.4.1. DNA Constraints to Site map: Exclude Makes and/or Models specified
18.7.4.1.1. For Make
18.7.4.1.2. For Model
18.8. US59398 & US58935
18.8.1. V1 & V2 Desktop and Mobile (Clicking model / make checkbox facets on facet search page should use new SEO friendly URL)
18.8.2. Automation Tests are covering this
18.8.3. Additional: Check the scenario that we didn't brake existing functionality on a make specific landing page ie: new-inventory/lincoln.htm