Solved problems. Proven solutions.

Choose the deployment mode based on control, crawlability, update frequency, and the client's hosting constraints. Static output is usually the most predictable when you can write files to the client host or deployment pipeline. The final HTML lives on the client domain, can be cached normally, and does not depend on runtime API availability. The tradeoff i…

Treat tenant identity as a required key at every layer. Data tables, content files, queues, media, API credentials, social connections, and publishing targets should all be scoped to a tenant/client ID rather than inferred from the current domain alone. Authorization checks should verify that the logged-in agency/user has access to that tenant before every…

Automate transformations while keeping editorial meaning under human control. On upload, store the original securely, extract dimensions/metadata, and generate derivative sizes appropriate to your design system. Serve responsive srcset/sizes so mobile devices do not download desktop-scale assets unnecessarily. Use modern formats where supported while preser…

Separate content identity from presentation destination. The CMS should store the content entity once, while each publishing channel has an explicit URL mapping and SEO policy. Do not put one universal hard-coded canonical URL on a content record that can legitimately render on multiple sites. Define a primary web canonical when the same public content is s…

Treat cache invalidation as part of publishing, not as an infrastructure afterthought. Map which caches can hold each page: application/object cache, full-page cache, reverse proxy, CDN, static artifact, browser cache, and any edge-rendered layer. Publishing should know which keys or paths need invalidation. Prefer targeted purge/revalidation for affected p…

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…

Model SEO as structured content and relationships, not a miscellaneous text box. At minimum, pages need a stable slug/URL strategy, title/H1 fields where editorial control is necessary, meta title/description overrides, indexability controls with safe defaults, canonical override only for exceptional cases, social image fields, and structured relationships…

Choose the simplest delivery mode that reliably serves the required page state and meets product constraints. For search-critical editorial, service, product, and location pages, the initial HTML response should ideally contain the primary content, title, canonical, robots directives, headings, and important internal links. Static generation and server-side…

Separate destination tracking from canonical product identity. The clean product URL should remain the canonical address used in internal links, structured data identifiers, XML sitemaps, and organic indexing. Merchant feeds can append approved tracking parameters for campaign attribution, but the landing page should declare the clean canonical when the tra…

Use the catalog hierarchy as the baseline, then add contextual merchandising paths where they help users. Primary navigation should expose major categories and important subcategories. Breadcrumbs should create a stable parent relationship from product back through its category path. Within category pages, link directly to canonical product URLs and avoid r…

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…

Prioritize differentiated value where it affects purchase decisions and search demand. Keep accurate manufacturer specifications, but add retailer-owned information that reflects real customer needs: fit/compatibility guidance, comparison context, installation notes, sizing, use cases, warranty/returns, shipping constraints, original photos/video, FAQs base…

Provide stable paginated URLs beneath the infinite-scroll experience. Each result page should be directly requestable and expose standard HTML links to products. The user interface can append results dynamically, but search discovery should not depend on scrolling events. Keep pagination canonical behavior consistent. Deeper pages generally should not all c…

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…

Use one product/inventory source of truth and generate each channel from that shared data. The visible product page, Product/Offer structured data, merchant feed, checkout state, and any API used by ads should derive price, currency, availability, identifiers, and variant relationships from the same current record whenever possible. Define update latency by…

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…

Demonstrate expertise inside the work. Use specific implementation details, constraints, tradeoffs, examples, and failure modes that would be difficult to produce from a superficial summary. Show how a recommendation changes under different conditions rather than presenting every tactic as universal. Where appropriate, include first-party evidence: screensh…

Score refresh candidates by opportunity, risk, and business value rather than age alone. Start with performance changes: declining impressions/clicks, lost query coverage, conversion changes, and competitors replacing the page for strategic terms. Pair that with content risk: outdated facts, expired product details, superseded regulations, broken links, sta…

Design each major section around a coherent subproblem. Use descriptive headings that state the subject of the section. Begin with a direct sentence or short paragraph that establishes the conclusion or definition, then add supporting explanation, evidence, examples, and edge cases. Repeat necessary entity names when context would otherwise be lost. A secti…

Write anchor text for navigation clarity first. The anchor should tell a reader what they will get after clicking. Use the natural name of the concept, page, product, service, or task. Exact-match wording is fine when it is the clearest label, but do not force the same phrase into every context. Vary wording naturally based on the surrounding sentence. A ca…

Query overlap alone is not proof of harmful cannibalization. First compare page intent. Two pages can legitimately appear for related queries if they solve different jobs—for example, a product page and a how-to guide. The problem is stronger when multiple URLs target the same intent and search systems alternate between them without a clear preferred page.…

Build the cluster around distinct user problems and content roles. Start with a topic map. Define the broad entity or problem space, then list the major intents inside it: definition, diagnosis, implementation, comparison, troubleshooting, cost, examples, tools, and advanced subtopics. Merge items that would produce substantially the same answer. Choose a h…

Information gain comes from adding evidence, decisions, examples, or structure that changes what the reader can understand or do. Before writing, inventory what the existing results already cover. Separate common baseline information from unanswered questions, unsupported claims, missing examples, outdated guidance, and contradictory recommendations. Then c…

Start with the page's job, not the keyword string. Define the primary intent in one sentence: what problem is the page supposed to solve, for whom, and at what stage of the journey? Then make the title tag communicate that value in the search result and make the H1 communicate the same page purpose to the visitor. They can be similar without being identical…

Use answer blocks where the page naturally needs a direct answer, not as a sitewide keyword template. Place a concise response immediately after a descriptive heading when the section addresses a specific question or decision. The first paragraph should stand on its own: define the concept, state the recommendation, or summarize the conclusion in plain lang…

Tie freshness signals to substantive changes and make those changes explainable. For high-change topics, assign an owner and review cadence based on risk. Product specifications, regulations, pricing, platform features, and rapidly changing technical guidance may need frequent review; stable definitions may not. Store both original publication date and last…

Create a consistent identity layer across the first-party site and authoritative external references. On the site, maintain a clear organization/about page with the canonical brand name, what the company does, primary website, headquarters or service model, leadership where appropriate, contact information, founding context, and links to official profiles.…

Start by analyzing the sources that are actually being selected. For a stable set of target questions, record cited domains and classify them: primary research, government/standards sources, specialist publications, community discussions, vendor documentation, comparison sites, or competitor pages. Then compare what those sources provide that your page does…

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…

Measure AI visibility as sampled coverage, not as a universal rank position. Start with a controlled query set tied to real customer intents. Group prompts by problem, product/service category, comparison, informational question, brand/entity question, and local intent where relevant. Preserve the exact wording so tests are repeatable. For each observation,…

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…

Use a shared evaluation framework, not a shared ranking assumption. Create a stable query set grouped by intent: category discovery, “best”/comparison, how-to, problem diagnosis, local intent, brand facts, product facts, and expert/topic association. Keep the exact prompts versioned so month-over-month comparisons are meaningful. For each platform/run, reco…

Separate factual freshness from cosmetic timestamp changes. Classify content by change rate. Product specifications, prices, leadership, regulations, statistics, platform features, and market data may need frequent review. Foundational definitions or historical explanations may remain accurate for years. For change-sensitive pages, maintain a review schedul…

Build repeated, verifiable relationships between entities rather than relying on keyword frequency. On the site, connect the organization to identifiable authors/experts, products/services, research, documentation, locations, and topic hubs. Use clear author bios, About pages, stable profile URLs, and internal links that show who is responsible for which ex…

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…

Publish evidence others have a reason to reference, then participate in the real information ecosystem around your market. Original research is one of the strongest assets: benchmarks, surveys, anonymized platform data, case-study findings, methodology papers, or recurring industry reports. Make the methodology transparent so journalists and experts can eva…

Design sections around complete information units. Each major section should have a descriptive heading and answer one coherent subproblem. Open with the main point, then add explanation, evidence, examples, and edge cases. A retrieved passage should make sense even if the reader did not see the previous section. Use explicit nouns and entities. Instead of…

Treat structured data as a machine-readable reinforcement layer, not a substitute for content, authority, or corroboration. Schema can make entity relationships explicit: who published an article, which organization owns a brand, where a local business is located, which product has a given identifier, what an FAQ or how-to section represents, and how pages…

Treat the incorrect answer as an entity-resolution problem. List each wrong or ambiguous fact and identify the likely entity it was confused with. Then search the web for sources supporting both the correct and incorrect versions. Build an entity evidence map covering the official website, About/Contact/Location pages, Organization/LocalBusiness schema, maj…

Make the page easy to understand at both document and passage level. Lead important sections with a direct answer before expanding into nuance. Use descriptive headings that match real questions and concepts. Keep paragraphs focused so a retrieved passage contains enough context to be useful without requiring three preceding sections. Support claims with ev…

Start with the information system that AI products can retrieve and corroborate, not with platform-specific hacks. 1. Define the entities. Establish the brand, products/services, people, locations, and relationships you want machines to understand. Use stable names, URLs, descriptions, and identifiers. 2. Build source consistency. Your website, profiles, au…

Use geographic sampling and query segmentation instead of one city-level rank. For proximity, measure the same query from a grid of points across the actual service market. Record distance to the business and the resulting local visibility. This shows where proximity likely dominates and where the listing can compete farther away. For relevance, compare per…

Focus on links that reflect real local relationships, expertise, and community participation. Start with existing business relationships: chambers, professional associations, suppliers, distributors, local sponsorships, nonprofit partnerships, schools, event organizations, and complementary businesses. Many companies already have legitimate relationships th…

Create a query-to-URL map before deciding that multiple ranking URLs are automatically a problem. Healthy overlap can occur when different URLs appear for different intents, neighborhoods, service variants, or stages of the journey. Cannibalization becomes harmful when two pages repeatedly compete for the same query set and neither establishes a stable role…

Inventory every profile before taking action. Record profile URL, name, address, phone, category, ownership status, review count, verification state, and whether it represents a location, practitioner, department, or historical location. Then classify the relationship: - True duplicate of the same business/location. - Legitimate practitioner profile. - Legi…

Build review generation into the customer workflow rather than running occasional campaigns. Define one legitimate trigger per service type: completed appointment, delivered project, resolved support case, or another point when the customer has actually experienced the service. Send the request consistently rather than only to customers staff believe are ha…

Model the company and each physical location as related but distinct entities. Create a stable Organization entity representing the brand/company, usually with a persistent @id tied to the canonical corporate/home URL. Then create one LocalBusiness entity for each legitimate location, each with its own stable @id, address, phone, geo coordinates when approp…

Prioritize citations by authority, visibility, and data-propagation impact. Start with owned and high-trust sources: Google Business Profile, the website, Apple Business Connect, Bing Places, major mapping/navigation platforms, primary social profiles, and industry-specific platforms customers actually use. Next identify data aggregators or ecosystem source…

Diagnose local visibility as a set of variables rather than one “GBP ranking” metric. First verify the profile is live, verified, policy-compliant, and not experiencing a suspension, duplicate, merged listing, category change, address/service-area change, or ownership issue. Then segment the visibility drop by query and geography. A grid rank tracker can re…

Start with a geographic hierarchy tied to real demand and service capability. Define the core service pages first. Then create service-area pages only for markets where the business truly operates and where there is enough unique context to justify a standalone landing page. Use a consistent URL pattern such as /service/city/ or /locations/city/service/ dep…

Build local search from one consistent business/entity model before expanding pages. 1. Establish the canonical business facts: legal/brand name, public-facing name, primary phone, primary website, physical address or service-area status, hours, primary/secondary categories, services, and key geographic markets. 2. Align the Google Business Profile with rea…

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…