E-E-A-T & Content Quality Reference

E-E-A-T Scoring Framework

Experience (20% weight)

Expertise (25% weight)

Authoritativeness (25% weight)

Trustworthiness (30% weight)

December 2025 Core Update Impact

Key Changes

• E-E-A-T now applies to ALL competitive queries, not just YMYL
• Anonymous/generic authorship penalized even for non-YMYL content
• Experience elevated as key differentiator (first-person narrative required)
• AI-generated content without genuine E-E-A-T signals actively demoted

Traffic Impact by Industry (Dec 2025)

Recovery Playbook

1. Add author bylines with verifiable credentials to all content
2. Implement ProfilePage schema for authors
3. Add first-hand experience signals (original images, case studies, test results)
4. Update publication dates and add "last reviewed" dates
5. Add editorial process documentation (about page, methodology)
6. Build external authority signals (guest posts, PR, conference talks)

AI Content Assessment

Google's stance (Sept 2025 Quality Rater Guidelines):

• AI content is acceptable if it demonstrates genuine E-E-A-T
• AI content is penalized when:
  • Generic phrasing without unique value
  • No first-hand experience signals
  • Factual errors or hallucinations
  • Mass-produced without editorial review
  • Duplicative of existing content without added perspective

AI Content Quality Checklist

• Contains original insights not available elsewhere
• Includes first-hand experience (photos, case studies, specific examples)
• Factually verified by subject matter expert
• Author byline with verifiable credentials
• Unique perspective or angle on the topic
• Edited for style, voice, and accuracy (not raw AI output)

Content Quality Gates (Extended)

Word Count by Page Type

Title Tag Requirements

• 30-60 characters (Google truncates ~60)
• Primary keyword near beginning
• Unique per page (no duplicates across site)
• Brand at end (optional, e.g., "| Brand Name")
• No keyword stuffing or pipe-separated keyword lists

Meta Description Requirements

• 120-160 characters (Google truncates ~155-160)
• Include a clear call-to-action
• Unique per page
• Include primary keyword naturally
• Preview what the user will find on the page

Image Alt Text Requirements

• 10-125 characters
• Describe the image content, not the filename
• Include keywords naturally (not forced)
• Decorative images: use alt="" or role="presentation"
• Functional images (buttons, links): describe the action, not the image

Content Freshness Signals

Update Tiers

Freshness Indicators

• <meta property="article:published_time"> and article:modified_time
• Schema datePublished and dateModified in Article/BlogPosting
• Visible "Last updated: [date]" on page
• <lastmod> in XML sitemap matching actual content changes

Helpful Content System (March 2024)

• Merged into core algorithm during March 2024 update
• No longer a separate HCU classifier
• Helpfulness signals weighted within every core update
• Key factors: satisfies search intent, provides unique value, demonstrates experience

Topic Cluster Architecture

Pillar-Spoke Model

[Pillar Page: "Complete Guide to X"]
    |
    |-- [Spoke: "X for Beginners"]
    |-- [Spoke: "Advanced X Techniques"]
    |-- [Spoke: "X vs Y Comparison"]
    |-- [Spoke: "Best X Tools in 2026"]
    |-- [Spoke: "X Case Studies"]

Rules:

• Pillar page covers the broad topic comprehensively (3,000+ words)
• Spoke pages go deep on subtopics (1,500+ words each)
• Pillar links to all spokes, spokes link back to pillar
• Spokes link to related spokes (lateral connections)
• Each spoke targets a distinct keyword cluster (no cannibalization)

Cannibalization Detection

Check Google Search Console for:

1. Multiple URLs ranking for the same query
2. Rankings fluctuating between pages (position volatility)
3. Neither page ranking well (split authority)

Fix: Consolidate content into the stronger page, 301 redirect the weaker page.

Internal Linking Strategy

Guidelines

• Every page should be reachable within 3 clicks from homepage
• Use descriptive anchor text (not "click here" or "read more")
• Link contextually within body content (not just navigation)
• Distribute links to important pages (more internal links = more crawl priority)
• Avoid excessive links per page (>100 internal links dilutes per-link value)

Hub-and-Spoke Pattern

• Hub pages (categories, pillars) link down to detail pages
• Detail pages link up to hub and sideways to related detail pages
• Breadcrumbs provide consistent upward navigation
• Related posts/products sections provide lateral discovery

Framework-Specific SEO Patterns

Next.js

• Use generateMetadata() for dynamic pages
• metadataBase for canonical resolution
• robots.ts for programmatic robots.txt
• sitemap.ts for dynamic sitemap generation
• Image component with priority prop for LCP images
• next/font for CLS-free web fonts

Nuxt

• useSeoMeta() composable for reactive metadata
• useHead() for canonical and hreflang links
• @nuxtjs/sitemap module for automatic sitemaps
• nuxt-og-image for dynamic OG images
• NuxtImg component for optimized images

Astro

• Layout-based metadata with props
• @astrojs/sitemap integration
• Static site generation by default (best for SEO)
• <Image> component for optimization
• Partial hydration keeps pages fast (minimal JS)

Remix

• meta export function per route
• links export for canonical tags
• Server-side rendering by default
• Nested routes for layout inheritance

GEO, AEO & AI Search Optimization Reference

Generative Engine Optimization (GEO)

How AI Search Works

AI search engines use Retrieval-Augmented Generation (RAG):

1. Retrieve: Query is converted to embeddings, matched against indexed web content
2. Augment: Top-matching passages are assembled as context
3. Generate: LLM synthesizes an answer, citing source passages

Unlike traditional search (10 blue links), AI search produces a single synthesized answer with inline citations. Visibility depends on being selected as a citation source.

Citation Mechanism

AI selects citations based on:

• Semantic relevance: Content closely matches the query intent
• Authority signals: Brand recognition, domain authority, entity presence
• Content structure: Self-contained passages, clear headings, data points
• Unique value: Original data, expert perspective, primary source

Key Statistics (2025-2026)

GEO Analysis Criteria (Weighted)

Princeton GEO Research Findings

Content Optimization for AI Citation

Do:

• Write self-contained paragraphs (134-167 words) that answer specific questions
• Include statistics with attribution ("According to [source], X is Y%")
• Add expert quotes and named attributions
• Use semantic HTML headings (H2 for questions, H3 for sub-answers)
• Include data in tables (AI extracts tabular data well)
• Provide clear definitions for technical terms
• Keep content factual and verifiable

Don't:

• Rely on visual elements alone (AI cannot see images)
• Use vague language ("many experts say", "studies show")
• Bury answers in long paragraphs without structure
• Use client-side rendering for important content
• Assume all AI platforms index the same way

Platform-Specific Optimization

Google AI Overviews

• Sources from Google's own web index (Googlebot)
• 92% of citations from top-10 ranking pages
• Traditional SEO is prerequisite
• Schema markup improves selection probability
• Blocking Google-Extended does NOT affect AI Overviews (uses Googlebot)

Google AI Mode (May 2025)

• Separate tab in Google Search
• Available in 180+ countries
• Zero organic blue links - AI citation is the ONLY visibility mechanism
• Content must be in Google's index to be cited

ChatGPT Web Search

• Sources from Bing web index (not Google)
• Also pulls from: Wikipedia, Reddit, Yelp, TripAdvisor, BBB
• GPTBot crawls for training data; ChatGPT-User browses in real-time
• Blocking GPTBot blocks training but NOT real-time browsing
• Only 11% domain overlap with Google AI Overviews

Perplexity

• Sources from its own web index + Bing
• Heavy Reddit sourcing, 40% more from high-authority sources
• Averages 21.87 citations per question (Qwairy study)
• Provides inline citations with page titles
• PerplexityBot crawls for indexing
• Respects robots.txt (blocks = no Perplexity visibility)

Bing Copilot

• Sources from Bing index exclusively
• Integrated into Bing search results
• Strong Enterprise usage (Microsoft 365 integration)

AI Crawler Management

robots.txt Directives

# Allow AI crawlers for visibility in AI search results
User-agent: GPTBot
Allow: /blog/
Allow: /docs/
Disallow: /proprietary/
Disallow: /internal/

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

# Block AI training but allow search
User-agent: Google-Extended
Disallow: /  # Blocks Gemini training, NOT Google Search/AI Overviews

User-agent: Bytespider
Disallow: /  # ByteDance training, usually safe to block

User-agent: CCBot
Disallow: /  # Common Crawl, optional

Decision Framework

Adoption: ~3-5% of sites currently use AI-specific robots.txt rules (growing rapidly).

llms.txt Standard

Emerging specification (December 2025) for providing structured content guidance to AI crawlers.

Format

# Example Company

> Brief description of the company/site

## Docs
- [Getting Started](https://example.com/docs/getting-started): Quick start guide
- [API Reference](https://example.com/docs/api): Complete API documentation

## Blog
- [Latest Updates](https://example.com/blog): Company news and insights

## Contact
- Support: support@example.com
- Sales: sales@example.com

Location

• File at domain root: https://example.com/llms.txt
• Markdown format
• Curated entry point (not exhaustive sitemap)
• Highlights most important/authoritative content
• Include contact and authority information

Checking for llms.txt

curl -sL "https://domain.com/llms.txt"
# 200 = implemented, 404 = not implemented

RSL 1.0 (Really Simple Licensing)

Machine-readable AI licensing standard (December 2025).

Purpose: Let content owners specify how AI systems may use their content.

Location: /.well-known/rsl.json

Backed by: Reddit, Yahoo, Medium, Quora, Cloudflare, Akamai, Creative Commons. Augments robots.txt with AI-specific granular permissions. Still emerging but gaining traction with major platforms.

Answer Engine Optimization (AEO)

Featured Snippet Formats

Paragraph snippet (most common):

• Question in H2/H3 heading
• Answer immediately after in a single paragraph
• 40-60 words (not too short, not too long)
• Direct answer first, then context

<h2>What is Core Web Vitals?</h2>
<p>Core Web Vitals are three performance metrics that Google uses as ranking
signals: Largest Contentful Paint (LCP) measures loading speed, Interaction to
Next Paint (INP) measures responsiveness, and Cumulative Layout Shift (CLS)
measures visual stability. Pages must meet all three thresholds to pass.</p>

List snippet:

• 5-8 items optimal
• Each item self-contained
• Use <ol> for ranked/ordered lists, <ul> for unordered
• H2/H3 heading with "best", "top", "steps", "ways"

Table snippet:

• 3-5 columns
• Semantic HTML with <thead> and <tbody>
• Comparison or data-oriented content
• H2/H3 heading describing what the table compares

People Also Ask (PAA) Targeting

• PAA boxes are dynamic and auto-populated based on query context
• Research: Use AlsoAsked.com, Google's PAA expansion, AnswerThePublic
• Target: Create question-based H2/H3 headings matching PAA questions
• Answer: Provide concise 40-60 word answer directly after heading
• Expand: Follow with detailed explanation below

Voice Search Optimization

• Queries are conversational (7-10 words average)
• Local/time-sensitive bias ("near me", "open now")
• Optimize: FAQ format, concise answers, conversational language
• Schema: LocalBusiness for local queries, Speakable for news
• Page speed critical (voice results typically from fast pages)

Speakable Schema

{
  "@context": "https://schema.org",
  "@type": "Article",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [".article-summary", ".key-findings"]
  }
}

• Currently Google News publishers only (English)
• Marks sections suitable for text-to-speech
• Max 30 seconds of audio when read aloud
• Use cssSelector (preferred) or xpath

Zero-Click Strategy

Many searches now resolve without a click (AI Overviews, featured snippets, knowledge panels).

Adapt by:

• Optimize for brand visibility even without clicks
• Include brand name in snippet-optimized answers
• Track impressions alongside clicks in GSC
• Build brand recognition that drives direct/branded searches later
• Accept lower CTR on informational queries, focus conversion on transactional queries

AI Search Visibility Monitoring

Manual Spot-Checking

1. Search your target queries in ChatGPT, Google (AI Overview), Perplexity
2. Note which sources are cited
3. Track whether your domain appears
4. Document monthly for trend analysis

Metrics to Track

• AI citation rate: % of target queries where you appear in AI answers
• Source diversity: Which AI platforms cite you (Google AIO, ChatGPT, Perplexity)
• Citation position: Where in the AI answer your citation appears (higher = better)
• Brand mention frequency: How often your brand is named in AI responses
• Impression-to-click ratio: GSC impressions vs clicks (declining ratio = more zero-click)

Emerging Tools

• AI search monitoring tools are rapidly evolving
• Baseline tracking now, formal tools expected to mature in 2026
• Use manual tracking + GSC data as primary signals

Link Building & Off-Page Reference

Toxic Link Patterns

Definite Spam (Auto-Flag for Disavow)

Likely Spam (Manual Review Required)

Potentially Problematic (Monitor)

Anchor Text Distribution

Healthy Benchmarks by Industry

Red line: Exact-match keyword anchor >15% = Penguin algorithm penalty risk.

Analysis Process

1. Export all backlinks with anchor text
2. Categorize each anchor into types above
3. Compare ratios against industry benchmarks
4. Flag if exact-match exceeds 15%
5. Check for patterns (same anchor from multiple domains = likely purchased)

Link Velocity Red Flags

Disavow File Format

# Disavow file for example.com
# Generated: 2026-04-01
# Review: Quarterly

# Spam domains (PBN network identified March 2026)
domain:spamsite1.com
domain:spamsite2.com
domain:linkfarm-network.com

# Individual toxic URLs
https://example-directory.com/paid-listing-page
https://hacked-site.com/injected-pharma-page

# Expired domain re-registrations
domain:expired-domain-spam.com

Disavow Decision Framework

Important: Only submit disavow if you have evidence of penalty or significant toxic patterns. Over-disavowing can remove beneficial links.

Link Acquisition Strategies

1. Digital PR (Highest Value)

Process:

1. Create a linkable asset (original research, data study, survey, tool, infographic)
2. Identify 50-100 journalists/bloggers covering your topic
3. Write personalized outreach (reference their recent work)
4. Pitch the story angle, not just the link
5. Follow up once after 3-5 business days

Success metrics: 5-15% response rate, 2-5% placement rate is good.

Linkable asset types by effectiveness:

• Original data/research studies (highest)
• Interactive tools and calculators
• Comprehensive industry reports
• Expert roundups with unique insights
• Visual content (infographics with unique data)

2. Resource Page Link Building

Process:

1. Search intitle:"resources" + [your topic] or inurl:resources + [your niche]
2. Find pages that curate links to useful resources
3. Verify the page is actively maintained (check last update)
4. Ensure your content genuinely adds value to their list
5. Email the page owner with a specific suggestion for where your link fits

3. Broken Link Building

Process:

1. Find resource pages in your niche (same as above)
2. Check outbound links for 404s (browser extension or crawl tool)
3. Create or identify your content that replaces the broken resource
4. Email: "I noticed [broken link] on your [page]. I have a similar resource at [URL] that covers [topic]."

Response rate: Typically 5-10% (higher than cold outreach because you're solving a problem)

4. Guest Posting

Site vetting checklist:

• Has real organic traffic (not just domain authority)
• Publishes content relevant to your niche
• Has editorial standards (rejects low-quality submissions)
• Links are contextual within content (not author bio only)
• Not a "write for us" link farm (check if they accept everything)

5. Unlinked Brand Mentions

Process:

1. Set up Google Alerts for your brand name, product names, key personnel
2. When a mention appears without a link, email: "Thanks for mentioning [brand]. Would you consider adding a link to [URL] for your readers' convenience?"
3. Focus on mentions in editorial content, not comments or forums

Success rate: 10-20% (highest of all strategies because they already know you)

Backlink Profile Health Score

Scoring Components

Score Interpretation

Free Backlink Data Sources

Key insight: Free sources combined capture 20-40% of raw backlink data but 60-70% of actionable intelligence (highest-authority links appear in free samples). For sites with <500 backlinks, free sources capture 50%+ of the meaningful profile.

Confidence Weighting for Multi-Source Analysis

Data sufficiency gate: Require 4+ of 7 scoring factors to produce a numeric health score. Otherwise report "INSUFFICIENT DATA" rather than misleading scores.

Competitor Backlink Gap Analysis

Process

1. Identify top 3-5 ranking competitors for your target keywords
2. Pull backlink profiles for each competitor
3. Find domains that link to 2+ competitors but NOT to you (= gap)
4. Prioritize gap domains by: relevance > authority > traffic
5. Create content that earns links from gap domains
6. Outreach with content that adds value to their audience

Gap Prioritization

Local SEO Signals Reference

Whitespark 2026 Local Ranking Factors

Factor Group Weights

Top 15 Local Pack Factors (Whitespark)

Proximity Data (Search Atlas ML Study)

• Proximity accounts for 55.2% of ranking variance in local pack
• For "near me" queries, proximity weight increases to ~65%
• For branded queries, proximity weight drops to ~30% (brand strength compensates)

Review Benchmarks

Volume & Velocity

• Magic 10 threshold: Significant ranking boost at 10 reviews (9 -> 10 = noticeable jump)
• 18-day rule: Rankings cliff if no new reviews for 3 weeks (velocity > volume)
• Monthly target: 2-4 new reviews/month minimum to maintain velocity signal
• Competitive threshold: Match or exceed top 3 competitors in review count

Quality Signals

• Average rating of 4.0+ expected (below 4.0 = conversion drop and potential ranking penalty)
• BrightLocal 2026: 74% only consider reviews from last 3 months
• BrightLocal 2026: 31% only use businesses with 4.5+ stars
• Reviews with photos weighted more heavily (Sterling Sky)

Review Platform Usage (BrightLocal 2026)

Review Management Rules

• Ask at peak satisfaction (post-service, positive interaction)
• Never incentivize reviews (violation of Google guidelines)
• FTC Consumer Review Rule (Oct 21, 2024): Penalties up to $53,088/violation for fake reviews, review gating, or suppressing negative reviews
• Review gating prohibited by both Google (fake engagement policy) and FTC
• Respond to ALL negative reviews within 24 hours
• Keep responses professional, address concerns, offer resolution
• Owner response rate target: 80%+
• Google removed 240M+ policy-violating reviews in 2024 (40% increase in enforcement)
• Review deletion rates up 600%+ (Jan-Jul 2025); 38% of deleted were 5-star

Fake Review Detection Signals

• Uniform timing patterns (reviews at same time of day/week)
• Limited reviewer history (single-review accounts)
• Geographic inconsistencies (reviewer location far from business)
• 5-star velocity spike (sudden burst of perfect scores)
• Identical or near-identical text across reviews
• Sudden volume spike after period of inactivity

Citation Source Tiers

Tier 1 - Universal (Must Have)

Tier 2 - Broad Directories

BBB, YellowPages, Manta, Superpages, Foursquare, Nextdoor, TripAdvisor (hospitality), Healthgrades (healthcare), Avvo (legal), HomeAdvisor (home services)

Tier 3 - Data Aggregators

Key: Fix aggregator data first. Incorrect aggregator data propagates errors to 70+ directories.

GBP Optimization Guide

Critical Fields (Direct Ranking Impact)

Important Fields

Supplementary Fields

Industry Weight Multipliers

NAP Consistency Audit

NAP = Name, Address, Phone. Must match EXACTLY across:

1. Website (HTML text, not just images)
2. Schema markup (LocalBusiness)
3. Google Business Profile
4. All citation sources
5. Social media profiles

Common Discrepancies

Audit Process

1. Search your business name in Google (check knowledge panel)
2. Check Tier 1 citations: GBP, Apple, Bing, Facebook, Yelp
3. Check Tier 3 aggregators: Data Axle, Foursquare, Neustar
4. Use a tool or manually verify top 20 citations match
5. Fix aggregator data first (cascades to downstream directories)
6. Allow 2-4 weeks for changes to propagate

Multi-Location Patterns

URL Structure

• Recommended: domain.com/locations/city-name/
• Bruce Clay study: 50%+ traffic lift vs subdomain structure
• Each location gets its own crawlable, indexable page

Location Page Requirements

• 60-70% unique content (below this = doorway page risk)

• Local photos (not reused across locations)
• Location-specific testimonials/reviews
• Unique service descriptions for the market
• Local team member bios
• Driving directions from local landmarks
• Nearby competitor differentiation

Doorway Page Risk Detection

RicketyRoo method: If you can swap the city name and the content still makes sense, it is a doorway page.

Example: HVAC company lost 80% rankings + 63% traffic post-March 2024 Core Update due to doorway-style location pages.

GBP Platform Changes (2025-2026)

• Diversity Update (2025): Harder to rank in both map pack AND organic simultaneously (Sterling Sky)
• Do NOT link GBP to your strongest-performing organic page (suppresses organic rankings)
• Link GBP to the specific location landing page
• Each location should have its own dedicated GBP listing
• Google Verified badge (Oct 2025): Replaces deprecated Guaranteed/Screened badges
• GBP Q&A deprecated Dec 3, 2025 (replaced by Ask Maps Gemini AI)
• GBP messaging removed July 2025
• Bing Places overhauled (Oct 2025): Now powers ChatGPT, Copilot, Alexa - critical for AI visibility
• Apple Business Connect doubled to 27% usage (BrightLocal 2026)
• Curated Local Lists (Local Gems, Trending) now appear around position 4 (SOCi, Nov 2025)

AI Impact on Local SEO (2026)

User Behavior Shift

• 45% of users now use ChatGPT/AI for local recommendations (up from 6%)
• ChatGPT conversion: 15.9% vs Google organic: 1.76% (Seer Interactive)
• AI-driven local discovery growing fastest among 18-34 demographic

Where AI Sources Local Data

Key insight: ChatGPT does NOT pull from GBP directly. Bing Places and third-party reviews are the path to ChatGPT local visibility.

AI Visibility Factors (Whitespark 2026)

• 3 of top 5 AI visibility factors are citation-related
• Dedicated service pages = #1 local organic factor AND #2 AI visibility factor
• Review volume and recency matter for AI recommendations
• Structured data (LocalBusiness schema) improves AI entity recognition
• AI Overviews appear on up to 68% of local searches (Whitespark Q2 2025)
• AI-powered local packs show 1-2 businesses, 32% fewer results (Sterling Sky)
• Local pack ads grew to 22% of results in 12 months (Sterling Sky/Places Scout)
• Zero-click rate for local-intent searches: up to 78% on mobile (Similarweb)
• "Near me" searches leading to visit in 24h: 76% (Google confirmed)
• 46% of all Google searches seek local information

Voice Search & Assistant Data Sources

• 58% of voice searches are for local business info (BusinessDasher)
• Google Assistant: GBP data (transitioning to Gemini)
• Siri: Apple Business Connect + Yelp
• Alexa: Bing Places + Yelp + data aggregators

Geo-Grid Rank Tracking

Simulates searches from multiple GPS coordinates to visualize local ranking coverage.

Share of Local Voice (SoLV): (top_3_count / total_grid_points) * 100

• 80-100%: Dominant
• 60-79%: Strong
• 40-59%: Moderate
• 20-39%: Weak
• 0-19%: Critical

Schema Types Full Reference

Active Schema Types (2026)

Content Types

Business & Organization

E-commerce

Navigation & Structure

Events

Other Active Types

Deprecated / Restricted Types - NEVER Recommend

Recent Additions (2024-2026)

• ProfilePage (2025) - For author E-E-A-T signals, mainEntity with Person
• ProductGroup (2025) - E-commerce variant grouping with variesBy, hasVariant
• DiscussionForumPosting (2024) - Forum/community content structured data
• ConferenceEvent (Dec 2025) - Conference-specific events
• PerformingArtsEvent (Dec 2025) - Arts events
• Product Certification (April 2025) - Energy ratings, safety certifications on products
• LoyaltyProgram (June 2025) - Member pricing, loyalty card structured data
• Organization-level shipping/return (Nov 2025) - Set via Search Console without Merchant Center

Deprecated Business Types

• Attorney: Deprecated by Schema.org - use LegalService + Person with hasCredential
• VehicleListing: Rich results removed June 12, 2025 - use Car + Offer instead
• Book Actions: Deprecated then reversed, still functional as of Feb 2026

JSON-LD Examples

Article / BlogPosting

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Optimize Core Web Vitals in 2026",
  "description": "A practical guide to LCP, INP, and CLS optimization.",
  "image": "https://example.com/images/cwv-guide.jpg",
  "datePublished": "2026-03-15",
  "dateModified": "2026-03-28",
  "author": {
    "@type": "Person",
    "name": "Jane Smith",
    "url": "https://example.com/authors/jane-smith",
    "sameAs": ["https://twitter.com/janesmith", "https://linkedin.com/in/janesmith"]
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Inc",
    "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
  }
}

Product with Offers

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Wireless Noise-Canceling Headphones",
  "image": "https://example.com/headphones.jpg",
  "description": "Premium wireless headphones with active noise cancellation.",
  "brand": { "@type": "Brand", "name": "AudioTech" },
  "sku": "AT-WNC-100",
  "gtin13": "1234567890123",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": "234"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/headphones",
    "price": "299.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "priceValidUntil": "2026-12-31",
    "seller": { "@type": "Organization", "name": "Example Store" },
    "shippingDetails": {
      "@type": "OfferShippingDetails",
      "shippingRate": { "@type": "MonetaryAmount", "value": "0", "currency": "USD" },
      "deliveryTime": {
        "@type": "ShippingDeliveryTime",
        "handlingTime": { "@type": "QuantitativeValue", "minValue": 0, "maxValue": 1, "unitCode": "DAY" },
        "transitTime": { "@type": "QuantitativeValue", "minValue": 3, "maxValue": 5, "unitCode": "DAY" }
      }
    },
    "hasMerchantReturnPolicy": {
      "@type": "MerchantReturnPolicy",
      "applicableCountry": "US",
      "returnPolicyCountry": "US",
      "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
      "merchantReturnDays": 30,
      "returnMethod": "https://schema.org/ReturnByMail"
    }
  }
}

LocalBusiness

{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "@id": "https://example.com/locations/downtown#business",
  "name": "Downtown Family Dental",
  "image": "https://example.com/downtown-office.jpg",
  "telephone": "+1-555-123-4567",
  "url": "https://example.com/locations/downtown",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St, Suite 200",
    "addressLocality": "Portland",
    "addressRegion": "OR",
    "postalCode": "97201",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 45.52345,
    "longitude": -122.67890
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:00",
      "closes": "17:00"
    }
  ],
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "156"
  },
  "priceRange": "$$",
  "branchOf": { "@type": "Organization", "@id": "https://example.com/#org" }
}

BreadcrumbList

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Products", "item": "https://example.com/products/" },
    { "@type": "ListItem", "position": 3, "name": "Headphones", "item": "https://example.com/products/headphones/" }
  ]
}

FAQPage (Gov/Healthcare Only for Rich Results)

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What are the eligibility requirements?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Applicants must be 18 years or older and reside in the state."
      }
    }
  ]
}

Note: FAQPage rich results restricted to government and healthcare authority sites since August 2023. However, the schema still provides value for AI/LLM citation visibility across non-Google platforms.

Industry-Specific Schema Patterns

Restaurant

• Type: Restaurant (subtype of LocalBusiness)
• Add: servesCuisine, menu (URL), acceptsReservations
• Include hasMenu with MenuSection and MenuItem for rich menu display

Healthcare

• Type: MedicalClinic, Hospital, or Dentist
• Add: medicalSpecialty, physician Person entities with hasCredential
• Include NPI number in sameAs links

Legal

• Type: LegalService (NOT the deprecated Attorney)
• Add: Person with hasCredential for bar admissions
• Include practice area pages with areaServed

Real Estate

• Type: RealEstateAgent
• Include RealEstateListing with Offer for property listings
• Note: VehicleListing deprecated June 2025, use Product + Car instead

Validation Checklist

1. All required properties present per type
2. Content marked up is visible on the page (no hidden content)
3. JSON-LD is syntactically valid (test with jsonlint.com)
4. @context uses https:// (NOT http://)
5. All URLs are absolute (NOT relative paths)
6. Test with Google Rich Results Test (search.google.com/test/rich-results)
7. Test with Schema.org validator (validator.schema.org)
8. No deprecated types used
9. URLs use canonical form
10. Prices include ISO 4217 currency codes
11. Dates use ISO 8601 format (e.g., 2026-03-15T08:00:00-07:00)
12. @id used consistently for entity references across pages
13. No placeholder text in live schemas

Technical SEO Deep Reference

Crawl Budget Optimization

Crawl budget = crawl rate limit (server capacity) x crawl demand (freshness/importance).

Signals That Increase Crawl Demand

• Frequent content updates (genuine changes, not cosmetic)
• High PageRank / many inbound links
• Fresh sitemap <lastmod> dates (only when content actually changed)
• URL submitted via Indexing API or URL Inspection tool

Signals That Waste Crawl Budget

• Faceted navigation generating thousands of parameterized URLs
• Session IDs or tracking parameters in URLs
• Infinite scroll without paginated URLs
• Calendar widgets generating endless date URLs
• Soft 404s (200 status but error content)
• Redirect chains (3+ hops)
• Duplicate content accessible at multiple URLs

Crawl Budget Audit Process

1. Download crawl stats from GSC (Settings > Crawl Stats)
2. Compare crawled URLs vs indexed URLs (Coverage report)
3. Identify gap: URLs crawled but not indexed = waste
4. Check server logs for Googlebot activity patterns
5. Fix: consolidate parameters, add canonical tags, block low-value paths in robots.txt

Robots.txt Advanced Directives

# Standard structure
User-agent: Googlebot
Allow: /
Disallow: /admin/
Disallow: /search?
Disallow: /*?sessionid=
Disallow: /tag/*  # if tag pages are thin

# AI crawlers (opt-in/opt-out)
User-agent: GPTBot
Allow: /blog/
Disallow: /proprietary/

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Disallow: /  # Blocks Gemini training, NOT Google Search

# Always allow CSS/JS for rendering
User-agent: *
Allow: /static/
Allow: /_next/
Allow: /assets/

Sitemap: https://example.com/sitemap.xml

Common Mistakes

• Disallow: / on production (blocks entire site)
• Blocking /api/ paths that serve rendered content
• Using noindex in robots.txt (not a valid directive, Google ignores it)
• Forgetting trailing wildcards: Disallow: /search blocks /search but not /search?q=test - use Disallow: /search
• Testing with wrong User-agent (Google only honors Googlebot-specific rules for Googlebot)

Rendering Strategy Implementations

Next.js SEO Setup

// app/layout.tsx - Global metadata
import type { Metadata } from 'next'

export const metadata: Metadata = {
  metadataBase: new URL('https://example.com'),
  title: { default: 'Site Name', template: '%s | Site Name' },
  description: 'Site description',
  openGraph: { type: 'website', locale: 'en_US', siteName: 'Site Name' },
  robots: { index: true, follow: true },
  alternates: { canonical: '/' },
}

// app/blog/[slug]/page.tsx - Dynamic metadata
export async function generateMetadata({ params }): Promise<Metadata> {
  const post = await getPost(params.slug)
  return {
    title: post.title,
    description: post.excerpt,
    openGraph: { title: post.title, description: post.excerpt, images: [post.image] },
    alternates: { canonical: `/blog/${params.slug}` },
  }
}

Nuxt SEO Setup

<!-- pages/blog/[slug].vue -->
<script setup>
const { data: post } = await useFetch(`/api/posts/${route.params.slug}`)

useSeoMeta({
  title: post.value.title,
  description: post.value.excerpt,
  ogTitle: post.value.title,
  ogDescription: post.value.excerpt,
  ogImage: post.value.image,
})

useHead({
  link: [{ rel: 'canonical', href: `https://example.com/blog/${route.params.slug}` }],
})
</script>

Astro SEO Setup

---
// src/layouts/Base.astro
const { title, description, canonical, image } = Astro.props
---
<html>
<head>
  <title>{title}</title>
  <meta name="description" content={description} />
  <link rel="canonical" href={canonical || Astro.url.href} />
  <meta property="og:title" content={title} />
  <meta property="og:description" content={description} />
  {image && <meta property="og:image" content={image} />}
</head>
<body><slot /></body>
</html>

JavaScript SEO

Critical Rules

1. Google renders JavaScript but with delays (seconds to weeks). Critical content in JS may be indexed late.
2. Other search engines (Bing, Yandex) have limited JS rendering. SSR/SSG is safer for multi-engine visibility.
3. AI crawlers do NOT execute JavaScript. Content only in client-side JS is invisible to ChatGPT, Perplexity, Claude.
4. Canonical conflicts: If raw HTML differs from JS-injected canonical, Google may use EITHER. Keep them identical.
5. noindex + JavaScript: If raw HTML has noindex but JS removes it, Google MAY still honor the raw HTML noindex.
6. Structured data timing: Schema injected via JS faces delayed processing. Include in server-rendered HTML.

Debugging JS Rendering Issues

# Compare raw HTML vs rendered HTML
curl -sL "URL" > /tmp/raw.html
# Use Chrome: chrome://inspect -> Network conditions -> Googlebot UA
# Or use Google's URL Inspection tool "View Tested Page" -> compare HTML

# Check if content is in raw HTML
curl -sL "URL" | grep -c "target content phrase"
# If 0, content is JS-rendered only

Redirect Audit Patterns

Chain Detection

# Follow redirect chain and show each hop
curl -sIL "URL" 2>&1 | grep -E "^(HTTP/|location:)" -i

# Expected: single 301 -> 200
# Problem: 301 -> 301 -> 301 -> 200 (chain)
# Problem: 301 -> 302 -> 200 (mixed, breaks PageRank transfer)

Common Redirect Issues

URL Parameter Handling

Faceted Navigation Strategy

Sitemap Index Pattern

For sites with 50,000+ URLs:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/sitemap-pages.xml</loc>
    <lastmod>2026-03-15</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-blog.xml</loc>
    <lastmod>2026-03-28</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-products.xml</loc>
    <lastmod>2026-04-01</lastmod>
  </sitemap>
</sitemapindex>

Rules:

• Max 50,000 URLs per child sitemap
• Max 50MB uncompressed per file
• <lastmod> must be W3C datetime format
• Only include canonical, indexable URLs (no noindex, no redirects, no 404s)
• Gzip compression recommended for large sitemaps
• Submit sitemap URL in robots.txt AND Google Search Console

Orphan Page Detection

Orphan pages have no internal links pointing to them. They rely solely on sitemap discovery.

# Extract all internal links from a page
curl -sL "URL" | grep -oP 'href="(/[^"]*)"' | sort -u

# Compare sitemap URLs vs internally linked URLs
# URLs in sitemap but not linked = potential orphans

Fix: Add internal links from relevant parent/sibling pages. If the page has no logical parent, consider whether it should exist.

IndexNow Protocol

Instant URL submission for Bing, Yandex, Naver, Seznam (NOT Google - Google only uses sitemaps and URL Inspection).

# Submit URL via IndexNow
curl -X POST "https://api.indexnow.org/indexnow" \
  -H "Content-Type: application/json" \
  -d '{"host":"example.com","key":"YOUR_KEY","urlList":["https://example.com/new-page"]}'

• Generate key file at https://example.com/YOUR_KEY.txt containing the key
• Submit up to 10,000 URLs per request
• Supported by: Bing, Yandex, Naver, Seznam, Yep
• Useful for: new content, updated content, deleted content (pair with 410 status)

Tooling Updates (2025-2026)

• Lighthouse 13.0 (Oct 2025): Major audit restructuring with reorganized performance categories
• CrUX Vis replaced CrUX Dashboard (Nov 2025)
• LCP subparts added to CrUX (Feb 2025): TTFB + Resource Load Delay + Resource Load Time + Element Render Delay
• round_trip_time replaced effectiveConnectionType in CrUX (Feb 2025)
• Google Search Console 2025: AI-powered configuration, branded vs non-branded filter, hourly API data, custom annotations
• Content API for Shopping sunsets August 18, 2026 - migrate to Merchant API

Mobile-First Indexing

Since July 5, 2024, Google uses 100% mobile-first indexing. ALL sites crawled with mobile Googlebot exclusively. Desktop-only content is invisible to Google.

Checklist:

• Same content on mobile and desktop (no hidden content on mobile)
• Same structured data on mobile and desktop
• Same meta tags (title, description, robots) on mobile
• Responsive design or dynamic serving (not separate mobile URLs if possible)
• Touch targets >= 48x48px
• No horizontal scrolling
• Text readable without zooming (>=16px base font)