Solved problems. Proven solutions.

Treat llms.txt as an emerging convention, not a guaranteed ranking or crawling mechanism. It can be used as a curated machine-readable guide, but it should not replace normal site architecture, robots controls, sitemaps, or content quality. 1. Keep the website crawlable and understandable through standard HTML, links, canonicals, and structured data first.…

Prioritize by dependency, risk, business impact, and effort. Fix blockers before building assets on top of them. 1. Establish measurement and business goals so success can be observed. 2. Fix critical crawl/index/redirect/canonical issues that can prevent pages from performing at all. 3. Clarify entity, service, location, and conversion architecture so new…

The correct action depends on whether the product is expected to return and whether the URL still helps users. 1. Temporarily out of stock: keep the URL live, show availability honestly, preserve product information, and offer alerts or alternatives. 2. Discontinued with a direct replacement: consider a relevant redirect if the old product no longer has ind…

Preview URLs should be treated as nonpublic workflow resources unless there is a deliberate reason to expose them. 1. Require authentication or signed expiring tokens for private previews when feasible. 2. Send noindex via meta robots or X-Robots-Tag on any preview that can be reached without authentication. 3. Keep preview URLs out of sitemaps, navigation,…

Segment sitemaps by meaningful content type or site section when that helps monitoring and scale. More importantly, include only URLs the system believes are canonical and indexable. 1. Generate sitemap entries from published status plus indexability rules, not simply every database record. 2. Exclude redirects, noindexed pages, previews, embeds, duplicate…

The editor should preserve semantic structure while limiting markup that creates accessibility, design, or search problems. 1. Reserve the page H1 for the template when possible and let the editor use H2/H3 levels in a logical hierarchy. 2. Sanitize pasted HTML and remove unsupported scripts, event handlers, and excessive inline styling. 3. Require valid hr…

Canonical generation should be based on the public destination URL for the specific deployment mode, not the CMS storage or preview URL. 1. Store the client’s canonical site origin as configuration rather than deriving it from the CMS host. 2. Resolve the public route/slug and generate one absolute canonical from origin + final path. 3. Keep previews, embed…

Create one metadata rendering pipeline with a clear precedence order. Multiple plugins/components should not each independently print search metadata. 1. Define a source-of-truth object for title, description, canonical, robots, Open Graph, Twitter, and schema. 2. Set precedence such as explicit page override → content-type template → global fallback. 3. Re…

For critical landing pages, the initial response should contain enough information to identify, understand, link, and evaluate the page even before enhancement scripts run. 1. Return the correct status code, title, canonical, meta robots, viewport, and primary metadata server-side. 2. Include the H1 and primary body content in the server response whenever p…

Prioritize 404s by how they are discovered and whether they represent lost user or search value. Not every random bot request needs a redirect. 1. Fix internal broken links first. Your own site should not intentionally send users or crawlers to missing URLs. 2. Restore or redirect high-value historical URLs with backlinks, traffic, or known campaign use whe…

The risk is not the builder itself; it is the output. Audit the rendered page as HTML, CSS, JavaScript, and network requests rather than assuming a visually correct page is technically healthy. 1. Check heading structure and make sure decorative widgets are not generating multiple meaningless H1s. 2. Review hidden tabs, accordions, sliders, and mobile varia…

Each indexable location page should generally canonicalize to itself. A template-level canonical pointing every city to one parent URL tells search engines the local pages may be duplicates to consolidate. 1. Inspect the final rendered canonical on multiple city pages, not just the template source. 2. Confirm each intended local page returns 200 and has a s…

Do not change established URLs only for cosmetic reasons. A shorter slug is rarely worth migration risk if the existing URL is stable, indexable, and performing well. 1. Change the slug when there is a durable reason: incorrect taxonomy, rebrand, merged content, major information-architecture change, or unusable legacy format. 2. Map the old URL directly to…

Choose the action based on whether the underlying intent will return and whether the URL has lasting value. 1. For recurring seasonal pages, keep the same URL and update the content when the next season approaches. Avoid creating a new year-specific URL unless the year itself is meaningful. 2. For ended promotions with a close replacement, redirect to the r…

Schema can clarify entities and relationships that already exist on the page. It cannot substitute for missing content, weak relevance, poor authority, or a bad user experience. 1. Use schema to describe visible facts: organization, location, services, authors, products, articles, breadcrumbs, and other appropriate entities. 2. Keep names, URLs, addresses,…

Image SEO starts with usefulness and performance. Images should support the page, load efficiently, and be described accurately rather than turned into another keyword field. 1. Prefer original project, team, location, product, or process images when available. They provide evidence that stock photos cannot. 2. Resize and compress images to realistic displa…

“Discovered - currently not indexed” usually means Google knows the URL but has not prioritized fetching it yet. The cause can be crawl demand, site quality patterns, or an oversized set of low-value URLs. 1. Confirm the pages are linked internally and not only present in the sitemap. 2. Check whether the site launched a large batch of near-duplicate locati…

Search engines can handle slash variants, but allowing both to resolve independently creates unnecessary duplicate URLs and mixed signals. 1. Choose one URL convention for directory-like paths and apply it consistently. 2. Redirect the nonpreferred variant directly to the preferred URL with one hop. 3. Use the preferred form in internal links, sitemaps, can…

Most internal search-result URLs should not be treated as indexable landing pages because they are unstable, low-control, and can create large crawl spaces. Curated filter pages are different. 1. Separate user-generated search URLs from intentionally built landing pages. 2. Keep internal search pages out of XML sitemaps and generally use noindex when they s…

A CDN sits between the origin and search crawler, so edge behavior becomes part of the website’s SEO implementation. 1. Verify status codes and redirects from multiple locations. Edge rules can create loops or inconsistent hostname/protocol behavior. 2. Check cache keys. Query parameters, cookies, device variants, and language settings can accidentally serv…

A pre-launch checklist should prove that the public site is crawlable, indexable, canonical, measurable, and mapped correctly from any previous URLs. 1. Remove staging noindex directives, HTTP authentication, and robots rules that should not reach production. 2. Verify canonical URLs, HTTPS, preferred hostname, trailing-slash rules, and redirect behavior. 3…

Pagination should preserve crawlable access to deeper items while avoiding misleading canonicalization. Page 2 is not usually a duplicate of page 1 because it contains different items. 1. Give each pagination URL a stable crawlable URL and generally let it self-canonical when it represents a real page in the sequence. 2. Do not canonical every paginated pag…

Duplicate titles are usually a symptom of duplicate page purpose rather than a penalty by themselves. They become important when several URLs are difficult to distinguish in search or in your own architecture. 1. Group duplicate titles by template and inspect whether the underlying pages have distinct intent. 2. If pages are true duplicates, consolidate the…

Use the redirect code that matches the intended duration of the move. Search engines can interpret both, but clear intent reduces ambiguity and keeps maintenance understandable. 1. Use 301/308 when the old URL is permanently replaced and you want users and search systems to adopt the new destination. 2. Use 302/307 when the original URL is expected to retur…

Treat a theme change like a controlled release because presentation-layer code often carries important search signals. 1. Crawl before and after deployment and compare status codes, canonicals, titles, meta robots, headings, internal-link counts, and structured data. 2. Check source HTML and rendered DOM for content that became JavaScript-dependent or disap…

Find orphan pages by comparing multiple URL sources rather than relying on one crawler. 1. Crawl the site from the homepage and export every discovered internal URL. 2. Export XML sitemap URLs, CMS content records, Search Console landing pages, analytics landing pages, and backlink-target URLs. 3. Normalize protocol, hostname, trailing slashes, and paramete…

A 200 status only says the server delivered a document. Search engines can still decide the document looks like an error, empty result, unavailable item, or low-value placeholder. 1. Check the visible content. Pages saying “not found,” “no results,” “product unavailable,” or showing only navigation can be classified as soft 404s. 2. Compare the title, H1, a…

Create a deployment health check that evaluates both content and rendered technical output. At the page level, validate final URL/slug, title, H1, meta robots, canonical, Open Graph basics, structured data parsing, primary image availability, and required entity fields. Confirm the canonical is on the allowed client domain and that noindex is intentional. R…

Treat llms.txt as an optional machine-readable orientation layer, not as a substitute for crawlable, authoritative web content. If you use it, keep it concise and accurate. Point to canonical documentation, important resources, product/service explanations, policies, and other durable pages that help a machine or developer understand the site. Maintain the…

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…

Treat infinite scroll as a user-interface enhancement layered on top of crawlable paginated states. Every chunk of results should have a stable URL that can be requested directly without requiring a user to scroll or click. Those URLs should return meaningful HTML, appropriate status codes, and consistent canonical behavior. The application can progressivel…

Classify parameters by function before choosing a control. Different parameter types need different treatment. Tracking parameters such as campaign IDs usually do not change page content. Internal links should avoid them, canonical should point to the clean URL, and server or edge rules can sometimes strip known parameters when doing so will not break attri…

Treat structured data as a graph of recurring real-world entities, not as a collection of independent snippets. Assign stable @id values to entities that persist across pages. For example, the organization can use a canonical homepage fragment ID, a real location can use its location-page URL plus an entity fragment, and an author can use the professional p…

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 llms.txt as an optional publisher-provided discovery/context aid, not as a universal AI indexing or ranking control. The format can be useful for pointing automated systems toward important documentation, canonical reference pages, or a concise map of a site's information architecture. For documentation-heavy sites, that can be operationally useful ev…

Start by classifying facet combinations by search value and uniqueness instead of applying one global rule. Create a facet matrix with dimensions such as category, brand, size, color, location, price, availability, and sort order. For each combination class, decide whether it can produce a durable landing page with distinct inventory/content and measurable…

Separate syntax validation from semantic validation. First confirm the JSON-LD is valid and uses supported Schema.org types/properties. Then verify that the markup describes content visibly present on the page. Search engines may ignore technically valid markup that exaggerates, invents, or conflicts with the user-visible page. Check entity identity careful…

Validate hreflang as a graph of reciprocal canonical URLs, not as isolated tags. For every localized page, build the expected language/region cluster from a source-of-truth table. Each URL in the cluster should be indexable, canonical to itself, and return 200. Then verify that every member references every other intended alternate, including itself when ap…

Start with field data because Core Web Vitals are user-experience metrics, not lab-score contests. Segment CrUX/Search Console data by template, device class, geography if relevant, and URL group. Determine whether the issue is systemic or isolated. A product template with poor LCP requires a different fix from a sitewide third-party script creating INP pro…

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…

Make every major signal tell the same story. Canonical tags are only one input; they are much weaker when the rest of the site contradicts them. Start by choosing the one URL that should be the durable public version. Then align signals in this order: 1. Redirect nonpreferred URLs when they do not need to remain independently accessible. A clean server-side…

Treat log analysis as behavioral evidence, not a replacement for a site crawl. First isolate verified search-engine bot requests and normalize URLs before analysis. Remove obvious static assets unless they are part of the investigation, separate Googlebot Smartphone from other user agents, and group requests by template or URL pattern. Build four views: 1.…

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.…

SEO, AEO, and GEO are best viewed as complementary parts of the same search strategy. SEO (Search Engine Optimization) focuses on helping webpages become discoverable, understandable, and competitive in traditional search results. This includes technical SEO, content quality, internal linking, metadata, site architecture, authority signals, and local optimi…