Solved problems. Proven solutions.

Promote facets based on durable demand, inventory stability, uniqueness, and business value. Start with query research and internal search/filter usage to identify combinations people actually seek. Then check whether the facet produces enough stable inventory and unique context to function as a standalone landing page. Strategic facets should receive clean…

Handle the URL according to the product's expected future and whether a real replacement exists. For temporary stockouts, keep the product URL live if the product is likely to return. Clearly show availability, preserve useful specifications/reviews, offer notifications, and link to relevant alternatives. Keep structured data availability accurate. For perm…

Classify variants by whether they represent independently useful landing pages. If a variant has unique search demand, distinct content or specifications, a stable SKU, and can be purchased directly, it may deserve an indexable self-canonical URL. Examples can include materially different models, capacities, or product configurations. If color/size variants…

Each data source answers a different question, so disagreements are expected. A crawler tells you what your current site architecture exposes when requested under the crawler's configuration. It is excellent for status codes, internal links, canonicals, robots directives, rendered HTML comparisons, and template-wide patterns. Server logs tell you what bots…

Design sitemap segmentation around diagnostic cohorts, not arbitrary file-size boundaries alone. Create separate sitemap groups for meaningful templates and business states: products, categories, articles, locations, service areas, documentation, high-priority evergreen pages, and other major content types. If inventory is large, subdivide further by stable…

Create an automated "SEO render diff" for representative URLs on every important template. Capture two versions of each page: the raw HTTP response body and a browser-rendered DOM after the normal application settles. Extract a focused set of SEO-critical fields from both: title, meta robots, canonical, hreflang, H1, primary text, internal links, structured…

A soft 404 is usually a content/state problem, not a status-code mystery. First determine whether the URL represents a real, useful resource that should exist independently. Inspect the rendered main content. Common triggers include near-empty location pages, out-of-stock product pages with no replacement path, search-result pages with zero results, thin ca…

Do not manage Search Console as an error inbox. Start by defining the intended index state for each template and URL class, then compare Google's reported state with that expectation. Build a URL inventory with at least: canonical URL, template, HTTP status, robots state, canonical target, sitemap membership, internal-link count, last meaningful update, and…

Treat redirects as a data-mapping problem and test them before DNS or routing changes go live. Export all meaningful legacy URLs from analytics, Search Console, XML sitemaps, crawls, backlink tools, server logs, and important campaign lists. Deduplicate them into one migration inventory. Assign each old URL one explicit destination based on content equivale…

Choose the control based on the desired outcome. Use robots.txt when you want to reduce crawling of URL patterns that search engines do not need to fetch, but understand that blocked URLs can still appear in search if discovered through links. Robots.txt is a crawl directive, not a reliable deindexing mechanism. Use noindex when a URL may be crawled but sho…

Use XML sitemaps as controlled cohorts of URLs. Their value is not the submit button; it is the ability to compare indexing behavior across known groups. Create separate sitemap files for meaningful templates or business groups such as products, categories, articles, locations, service areas, and priority evergreen pages. Keep every sitemap limited to canon…

Use a fixed diagnostic order so you do not chase symptoms in random tools. 1. Start with the exact URL and establish the expected state. Decide whether the URL should be crawlable, indexable, canonical, and internally discoverable. Many audits become confused because nobody defines the intended state first. 2. Test raw HTTP behavior. Check status code, redi…

Diagnose indexing as a funnel: URL existence -> crawl access -> renderability -> canonical eligibility -> content value -> discovery/signals. 1. Confirm the exact URL returns a stable 200 response. Check redirects, soft-404 behavior, authentication, geofencing, and intermittent server errors. 2. Check robots controls at every layer: robots.txt, meta robots,…

Treat canonicalization as a cluster of signals. The HTML canonical tag is one input, and it can be outweighed by stronger contradictory signals. Debug in this order: 1. Compare the candidate URLs. Check content similarity, status codes, redirect behavior, trailing slashes, protocol/host variants, parameters, pagination, print views, and localized versions.…

Validate what the server returns, what the rendered DOM contains, and what search engines are actually indexing. Those are three different checkpoints. 1. Fetch the raw HTML without executing JavaScript. Confirm the response status, canonical, title, meta robots, structured data, primary heading, internal links, and ideally the primary body content. If the…