Loading…
Loading…
Make important pages accessible to people and search crawlers. This guide covers practical crawling, indexing, canonical, sitemap, structured data, and AI crawler considerations without promising rankings or inclusion in any search or AI product.
For Google to consider a page in Search, it must be discoverable, crawlable, and eligible for indexing. Many sites have technical barriers that prevent this process from working correctly — often without realizing it.
A sitemap is a discovery hint, not a directive or guarantee of crawling or indexing. Keep it within protocol limits and list preferred, canonical URLs that you want considered for indexing. Submit it in Search Console if useful and monitor the report for processing errors; submission does not force indexing.
Robots.txt controls crawler access, not privacy or indexing by itself. Avoid blocking important pages and resources Google needs to render them. A disallowed URL can still appear in results if discovered elsewhere. Use a crawlable noindex directive to exclude a public URL, or authentication for private content. Choose AI crawler rules based on the crawler's documented purpose and your policy.
Use a canonical link to indicate a preferred URL among duplicate or substantially similar pages. Google treats canonicals as a hint and may select another URL. Keep internal links, redirects, sitemap entries, and canonical tags consistent; a distinct page with useful content may deserve its own self-referencing canonical.
Crawl-budget work is usually not a priority for smaller sites. For large sites with many rapidly changing or duplicate URLs, review crawl activity and server capacity, reduce unnecessary URL variants, keep internal links consistent, and remove redirect chains. Do not block a URL in robots.txt when Google needs to crawl it to see a canonical or noindex directive.
Structured data communicates machine-readable context about your pages. It must match visible content and follow the specific feature's current requirements; validity alone does not make a page eligible for a rich result.
| Schema Type | Why It Matters | Priority |
|---|---|---|
Organization Organization | Describes an organization and its official details; does not guarantee a Knowledge Panel | Use when relevant |
WebSite WebSite | Identifies the website and its name; SearchAction no longer enables a Sitelinks Search Box | Use when relevant |
SoftwareApplication SoftwareApplication | Describes software; only use supported properties that are accurate and visible | Use when relevant |
Article Article | Provides structured article details; does not guarantee special search presentation | Use for articles |
BreadcrumbList BreadcrumbList | Describes a page's place in the site's hierarchy; result display is not guaranteed | Use when relevant |
Review / AggregateRating AggregateRating | Can support eligible review snippets when genuine, visible, and compliant; never add fabricated or self-serving ratings | Only when eligible |
Test markup with Google's Rich Results Test for Search feature eligibility and Schema.org's validator for vocabulary issues. These checks do not guarantee that Google will show a rich result.
Core Web Vitals are field metrics for loading, responsiveness, and visual stability. They are part of Google's page-experience signals, but scores alone do not guarantee rankings and are not a proxy for bounce rate.
LCP
Largest Contentful Paint
Primary fix: Preload hero image, use CDN, optimize image format (WebP/AVIF), reduce server response time
INP
Interaction to Next Paint
Primary fix: Reduce JavaScript execution time, defer non-critical scripts, minimize long tasks blocking main thread
CLS
Cumulative Layout Shift
Primary fix: Add explicit width/height to all images and videos, avoid inserting content above viewport content, preload fonts
AI products use different crawlers and sources, and their access and citation policies vary. No technical change guarantees that a page will be indexed, used in training, or cited in an AI-generated answer.
llms.txt is a community proposal, not a Google Search requirement or documented AI inclusion control. Adoption varies by service. If you publish one, keep it accurate and maintain it as optional documentation rather than prioritizing it over accessible, useful pages.
Use accurate product descriptions, clear authorship where relevant, and primary sources for factual claims. These are good publishing practices, but there is no proven checklist that guarantees citation or recommendation by an AI service.
Some services identify crawlers for search retrieval, while others identify crawlers used for model training. Review each provider's published documentation and your own policy before allowing or blocking a crawler. Google-Extended controls certain Gemini and Vertex AI uses; it does not control Google Search crawling or determine inclusion in Search or AI Overviews.
Allowing a crawler in robots.txt permits access under that crawler's rules; it does not ensure a service will use, index, train on, cite, or recommend your content. Robots directives are voluntary and are not a substitute for authentication or other access controls.
# Example robots.txt crawler controls
User-agent: * Disallow: /admin/ Disallow: /api/ Sitemap: https://example.com/sitemap.xml
Internal links help people and crawlers discover related pages and understand site structure. Make important pages reachable through useful navigation and contextual links; there is no universal number of links required for a page to rank.
Organize your content into topical hubs with a main pillar page (hub) and a cluster of supporting articles (spokes). The pillar page targets a broad, high-competition keyword. Each spoke targets a specific long-tail variant and links back to the hub. This architecture concentrates topical authority on your pillar pages and makes your site structure clear to both human readers and crawlers.
Your highest-traffic blog posts and landing pages should contain deliberate internal links to your product pages, pricing, signup, and other high-conversion destinations. A new user landing on your statistics post via organic search is a valuable prospect — make sure there is a clear, contextually relevant link to your product from within that content.
Link to useful pages from relevant navigation, category pages, or related content. Avoid orphan pages, but do not target an arbitrary number of links; prioritize clear paths for users and crawlable links.
Write concise link text that describes the destination in context. Avoid repetitive keyword-stuffed anchors and generic text when a clearer phrase helps readers understand where a link goes.
Use this checklist to review common implementation issues. Priorities vary by site; no checklist can guarantee that a page will be indexed or rank.
Use Google Search Console's URL Inspection tool for an individual URL's known indexing status, Google's selected canonical, and the last crawl information available. The Page indexing report helps investigate patterns across URLs. URL Inspection does not report Core Web Vitals or validate all structured data; use the relevant Search Console reports and Rich Results Test for those checks. A site: query is only a rough diagnostic, not a complete index count. Google decides whether a discovered and crawlable URL is indexed.
Crawling is when a crawler discovers and fetches a URL; indexing is Google's separate decision to store and potentially show a page in Search. A page may be crawled but not indexed, for example because it is a duplicate or Google does not consider it useful enough. A robots.txt disallow prevents Google from crawling that URL, but does not reliably prevent the URL from appearing in search results. If a page must be excluded, allow crawling so Google can see a noindex directive, or protect it with authentication. Neither crawling nor indexing guarantees rankings.
Use structured data only when it accurately describes visible page content and meets the relevant feature's rules. Organization, Article, Product, and BreadcrumbList markup can help machines interpret page details, but markup does not guarantee a rich result or ranking benefit. Review Google's current Search Gallery for supported Search features before implementation. FAQ rich results are generally limited to well-known government and health sites, HowTo rich results have been retired, and WebSite SearchAction no longer produces a Sitelinks Search Box. JSON-LD is a supported format, not a shortcut to eligibility.
Robots.txt gives compliant crawlers instructions about which URLs they may fetch; it is not access control and cannot guarantee a URL stays out of search results. Avoid accidentally disallowing important content or resources needed to render it. If a public page should be excluded from Google, do not block it in robots.txt: let Google crawl a noindex directive, or require authentication for private content. A blocked URL can still be indexed without a description, and link discovery or ranking effects are not reliably controlled by robots.txt.
llms.txt is a community proposal for a Markdown summary intended for language-model use. It is not a Google Search requirement or a documented way to get included in AI answers, and adoption by AI services varies. Treat it as optional documentation; do not prioritize it over accessible, useful pages, ordinary crawl controls, and clear sourcing, and do not promise that it improves citation or recommendation chances.
Google uses Core Web Vitals as part of its page-experience signals, alongside many other ranking systems; good scores do not guarantee better rankings. The current 'good' field thresholds are LCP ≤ 2.5 seconds, INP ≤ 200 milliseconds, and CLS ≤ 0.1, assessed at the 75th percentile. Measure real-user field data and improve issues that affect actual visitors. Do not treat bounce rate as a Google ranking metric or assume one performance score determines search visibility.
Parameters can create many URL variants, so keep internal links and sitemaps consistent and use a canonical only when a URL is a duplicate or alternate of the preferred page. A parameterized category page may be a valid indexable landing page if it has distinct value and a self-referencing canonical. Google's legacy URL Parameters tool is retired; it cannot be used to control crawling. Avoid blocking URLs that Google needs to crawl to see a canonical or noindex signal, and prioritize crawl-budget work only when site size and crawl activity make it relevant.
Use these references to validate implementation details, avoid stale assumptions, and keep your technical SEO stack aligned with current standards.
Google Search Central Documentation
Canonical technical guidance for crawling, indexing, structured data, and search quality.
Core Web Vitals - web.dev
Official metric definitions, thresholds, and implementation guidance for LCP, INP, and CLS.
Schema.org Vocabulary
Structured data type definitions used for JSON-LD implementation.
Google Rich Results Test
Validation tool to test rich result eligibility for structured data.
Google Search Central: Robots.txt
Explains crawler access rules and why robots.txt is not an indexing or privacy mechanism.
Google Search Central: URL Structure
Current URL and parameter guidance, including simple and crawlable URL structures.
Google Search Central: AI Features
Official guidance on how Google Search features powered by AI relate to Search eligibility.
robots.txt Specification (RFC 9309)
Formal robots exclusion protocol behavior and parsing rules.
A sound technical foundation helps people and crawlers access your pages, but search and AI services make their own inclusion decisions.