SEO Best Practices

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Content High Effort: Moderate

Demonstrate E-E-A-T Signals Throughout Your Content

Experience, Expertise, Authoritativeness, and Trustworthiness are the dimensions Google's quality raters use to evaluate content. Trust is the most important. These are signals you build into content, not metrics you can check in a dashboard.

Why It Matters

E-E-A-T is not a ranking algorithm or a score accessible in Search Console. It is a framework for evaluating content quality that Google's human quality raters apply, and that Google's automated systems are trained to approximate. Trust is the foundation: if a page cannot be trusted for accuracy, the other E-E-A-T dimensions are irrelevant. For YMYL (Your Money or Your Life) content covering health, finance, or safety, E-E-A-T signals receive heightened scrutiny because the consequences of poor information are material.

Key Principles

Experience refers to first-hand, lived experience with the subject matter. Review a product you have used; describe a process you have performed.
Expertise refers to knowledge and skill in the relevant domain, evidenced in the depth and accuracy of content, not merely claimed in an author bio.
Authoritativeness is built over time through recognition by others in the field: citations, links, and references from authoritative sources.
Trust is the most critical dimension and is undermined by factual errors, missing sources, hidden authorship, or a site that cannot be identified as legitimate.

Implementation

Specific, actionable steps to put this into practice.

Add visible authorship to content, with author bio pages that document credentials, published work, and relevant experience.
Cite primary sources, original research, and authoritative references throughout content rather than relying on unattributed claims.
Include publication dates and last-updated dates on all content so readers can assess how current the information is.

Verification

How to confirm this practice is correctly implemented.

Check whether every factual claim in your content is supported by a linked, verifiable source.
Evaluate your site against Google's Quality Rater Guidelines' E-E-A-T criteria, which are publicly available.
Review whether your About page, contact information, and author pages provide sufficient information to establish the site as legitimate.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Adding an author byline without an actual author page that documents credentials and professional context.
Publishing YMYL content without medical, legal, or financial professional review.
Conflating 'authoritative writing style' with expertise; confident language does not substitute for verifiable knowledge.

At a Glance

Impact High

Effort Moderate

Category Content

Primary Source

Google Search Central

Style Guide: Headings and Titles

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Content Medium Effort: Easy

Establish Logical Heading Hierarchy for Content Structure

Heading tags (H1 through H6) define content hierarchy for search engines and screen readers. One H1, then logical H2/H3 nesting, is the baseline standard.

Why It Matters

Logical heading hierarchy helps both users and search engines parse and understand content. Google uses headings to understand the main topics and subtopics of a page, providing critical semantic context. Furthermore, proper hierarchy is essential for web accessibility, allowing screen readers to navigate the document logically, which is also a factor in overall page quality evaluation.

Key Principles

Use exactly one H1 tag per page to define the primary topic or title of the document.
Use H2 tags for main sections, H3 tags for subsections within those, and so on, strictly following numerical order without skipping levels.
Headings should accurately describe the content immediately following them.

Implementation

Specific, actionable steps to put this into practice.

Ensure the H1 tag is highly relevant to the primary keyword and user intent for that page.
Break up long sections of text with descriptive H2 and H3 tags to make the content scannable.
Do not use heading tags purely for styling purposes (e.g., making text large and bold); use CSS for styling and HTML for semantics.

Verification

How to confirm this practice is correctly implemented.

Use browser extensions or SEO crawlers to extract and review the heading outline of a page.
Ensure the outline reads logically, similar to a table of contents for a book.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Skipping heading levels (e.g., jumping from an H1 directly to an H4), which breaks semantic structure.
Wrapping entire paragraphs or images in heading tags.

At a Glance

Impact Medium

Effort Easy

Category Content

Primary Source

Google Developers

Content High Effort: Hard

Establish Topic-Specific Expertise for Discover Traffic

To succeed in Google Discover, build deep, topic-specific expertise and local relevance rather than broad, general-interest content. Discover now operates under its own core update system with distinct ranking signals.

Why It Matters

Google's February 2026 Discover Core Update, the first of its kind, introduced specific ranking signals for the Discover feed. The algorithm now evaluates expertise on a granular, topic-by-topic basis rather than domain-wide. It also heavily prioritises content from publishers based in the user's country and actively demotes sensationalism and clickbait. Publishers relying on broad coverage or outrage-driven headlines saw immediate, sustained Discover traffic declines.

Key Principles

Discover expertise is topic-specific, not domain-wide.
Local relevance is a major structural ranking factor for Discover.
Clickbait and sensationalism are actively penalised.
Original, in-depth content is favoured over derivative news coverage.

Implementation

Specific, actionable steps to put this into practice.

Narrow your editorial focus to specific topics where you have demonstrable expertise.
Highlight local context, authors, and relevance in your content.
Enforce strict editorial guidelines against clickbait and exaggerated headlines.
Invest in original, in-depth reporting rather than derivative news coverage.
Create comprehensive content hubs around your primary subjects to signal depth.

Verification

How to confirm this practice is correctly implemented.

Monitor Discover traffic in Google Search Console's Performance report (filter by Search Type: Discover).
Track which specific topics and categories of content are surfacing in Discover.
Review which articles lost Discover impressions after the February 2026 update.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Publishing outside your core niche in an attempt to capture trending Discover traffic.
Using sensational headlines that do not accurately reflect the content.
Treating Discover as an extension of organic search rather than a distinct channel with its own signals.

At a Glance

Impact High

Effort Hard

Category Content

Primary Source

GOOGLE SEARCH CENTRAL

Google's February 2026 Discover Core Update

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Content High Effort: Easy

Keep Content Factually Accurate and Well-Sourced

Factual accuracy is the baseline of trust. A single demonstrably wrong claim on a page raises doubts about everything else on it and, by extension, about the site that published it.

Why It Matters

Google's ranking systems include fact-checking mechanisms and evaluate whether information is accurate according to established expert consensus, particularly for YMYL topics. Beyond algorithmic evaluation, factual errors damage reader trust, attract correction requests, and can generate negative coverage that harms brand credibility. For health, financial, or legal topics, inaccurate content can cause material harm to readers — which is why Google treats accuracy as a ranking consideration for these categories.

Key Principles

Every factual claim should be verifiable against a primary source or established expert consensus.
Sources should be cited inline, not collected in a generic references section at the bottom of the page.
Statistics and data should include publication dates; outdated statistics are a form of inaccuracy.
Content should be updated when new information supersedes existing claims.

Implementation

Specific, actionable steps to put this into practice.

Establish a fact-checking process for all published content: every claim requires a cited source before publication is approved.
Set review schedules for time-sensitive content: technology, health, and legal content should be reviewed at least annually.
When a factual error is identified, correct it promptly, update the last-modified date, and consider adding a visible correction note.

Verification

How to confirm this practice is correctly implemented.

Audit your highest-traffic pages for statistics and data points older than two years; verify whether they remain current.
Check whether your primary sources are still accessible and have not been retracted or updated with different findings.
Use a structured fact-checking process to verify all claims made without inline citations.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Citing secondary sources (articles about research) rather than the original research itself.
Using outdated statistics because they support a desired narrative.
Publishing AI-generated content without fact-checking the output against primary sources.

At a Glance

Impact High

Effort Easy

Category Content

Primary Source

Google Search Central

Best Practices for "Read more" Deep Links in Google Search

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Content Medium Effort: Easy

Optimise Content for "Read More" Deep Links in Search Results

"Read more" deep links are clickable links within search result snippets that lead users directly to specific sections of a page. Google displays these links when content is properly structured and accessible, increasing click-through rates by providing users with a direct path to relevant content.

Why It Matters

When Google displays a "read more" deep link in a search snippet, it provides an additional, eye-catching entry point to your page. Rather than users clicking on the main page title, they can click directly to the section most relevant to their query. This increases the likelihood of clicks to your site and improves user satisfaction by reducing the need to scroll or search within the page after landing.

Key Principles

Content must be immediately visible to a human visitor when the page loads, not hidden behind expandable sections, tabs, or other interactive elements.
The page structure must use semantic HTML headings and logical content organisation so Google can identify distinct sections.
Deep linking must work reliably; users must be able to navigate directly to the linked section without the page jumping or scrolling unexpectedly.

Implementation

Specific, actionable steps to put this into practice.

Ensure all important content sections are visible above the fold or easily accessible without user interaction on page load.
Use descriptive heading tags (H2, H3) to clearly delineate content sections that Google can identify as deep-linkable targets.
Avoid using JavaScript to manipulate scroll position on page load, as this prevents users from landing at the intended section when they click a "read more" link.
If using the History API or window.location.hash modifications, ensure the hash fragment remains in the URL so deep linking continues to work correctly.

Verification

How to confirm this practice is correctly implemented.

Monitor Google Search Console's "Performance" report to identify queries where "read more" deep links appear for your site.
Test deep links manually by clicking them in search results and confirming the page scrolls to the correct section.
Use browser developer tools to inspect the page structure and ensure headings are properly marked up and sections are semantically distinct.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Hiding content behind accordions, tabs, or "expand" buttons that require user interaction to reveal.
Using JavaScript to force the page to scroll to the top on load, which breaks the deep link and frustrates users.
Failing to preserve URL hash fragments when using modern JavaScript routing, which breaks the ability to link directly to sections.

At a Glance

Impact Medium

Effort Easy

Category Content

Primary Source

Google Search Central

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Content Medium Effort: Moderate

Optimise for Featured Snippets

Featured snippets are selected automatically by Google for queries where a direct answer is more useful than a list of links. Structuring content to provide clear, direct answers in the correct format significantly increases the probability of selection.

Why It Matters

Google's documentation confirms that featured snippets are "generated automatically" and that "being featured in a snippet is not a ranking factor for the page's position in regular search results." A page does not need to rank first to win a featured snippet — it needs to provide the clearest answer. For voice search, featured snippets are the primary source of responses. A page that wins a featured snippet for a voice-search query is the answer that Google Assistant reads aloud to users.

Key Principles

List snippets require numbered or bulleted HTML lists for step-by-step content
Table snippets require properly formatted HTML tables
Headings should mirror the query language

Implementation

Specific, actionable steps to put this into practice.

For each query, identify the snippet format (paragraph, list, or table)
Restructure the relevant content section to provide a direct answer in the correct format
Ensure the heading above the answer mirrors the query language
Monitor Search Console for featured snippet appearances following the change

Verification

How to confirm this practice is correctly implemented.

Monitor impressions and CTR in Search Console for featured snippet queries

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using prose for step-by-step content that should be a numbered list
Optimising for featured snippets on queries where the intent is navigational or commercial (these rarely trigger snippets)
Failing to monitor whether snippet wins are generating traffic (zero-click queries may not)

At a Glance

Impact Medium

Effort Moderate

Category Content

Primary Source

GOOGLE SEARCH CENTRAL

Featured Snippets and Your Website

Content High Effort: Hard

Prioritise First-Party Authority Over Content Aggregation

Build your site as the original source or official representative of a topic rather than relying on aggregating, hosting, or syndicating other people's content. Google now demonstrably favours the former over the latter.

Why It Matters

The March 2026 Core Update marked a fundamental reversal in Google's ranking priorities, severely penalising UGC platforms and aggregators while elevating first-party, brand-owned media properties. Lily Ray's empirical analysis of 2,000+ domains using SISTRIX data showed YouTube losing 567 visibility points in under two weeks, with Reddit, Instagram, and X suffering similar declines. Conversely, IMDB, Amazon, Apple, and government domains gained substantially. The pattern is unambiguous: Google is prioritising "the company that owns the thing" over "the platform people use to talk about the thing."

Key Principles

Original, first-party content is significantly favoured over syndicated or aggregated content.
Being a platform that hosts others' content is now a ranking disadvantage at scale.
Authority is tied to being the original creator or official source of a topic.

Implementation

Specific, actionable steps to put this into practice.

Shift content strategy away from aggregation towards original reporting, research, and first-party data.
For e-commerce sites, focus on unique product descriptions and first-party reviews rather than syndicated manufacturer content.
Build direct audience relationships rather than relying on third-party platforms for distribution.
Ensure your site is clearly the authoritative source for your core topic, not a commentary on it.

Verification

How to confirm this practice is correctly implemented.

Monitor organic traffic trends following major core updates.
Track rankings for high-value queries against competitor aggregator sites.
Review which pages gained or lost visibility after the March 2026 update.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Relying on UGC or forum-style content to drive organic growth.
Building a content model entirely around curating existing information without adding substantial original value.
Treating platform distribution (YouTube, Reddit) as a substitute for first-party owned properties.

At a Glance

Impact High

Effort Hard

Category Content

Primary Source

AMSIVE (LILY RAY)

Google March 2026 Core Update: Winners, Losers & Analysis

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Content Medium Effort: Moderate

Provide Unique Meta Descriptions for Critical Pages

Write compelling, page-specific meta descriptions to improve click-through rates and provide search engines with a high-quality summary option for the SERP snippet.

Why It Matters

While meta descriptions are not a direct ranking factor, they act as organic ad copy. A well-crafted description can significantly improve the click-through rate from search results. If Google finds the meta description more accurate than the on-page content, it will use it for the snippet.

Key Principles

Descriptions should inform and interest users, acting as a pitch for the page's content.
Identical or similar descriptions across multiple pages are unhelpful and often ignored by Google.
Descriptions can include structured data points like price, author, or publication date.

Implementation

Specific, actionable steps to put this into practice.

Write unique meta descriptions for the homepage, category pages, and high-traffic articles.
Ensure the description accurately summarizes the page content without relying on a list of keywords.
For large database-driven sites, use programmatic generation to create diverse, human-readable descriptions based on page-specific data.

Verification

How to confirm this practice is correctly implemented.

Use a crawler to identify pages with missing or duplicate meta descriptions.
Review search queries in Google Search Console to ensure the descriptions align with user intent.
Check live search results to see if Google is utilizing your provided description or overriding it with page content.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Leaving the meta description blank, forcing Google to pull potentially irrelevant text from the page.
Using a single, generic description across the entire site.
Stuffing the description with keywords rather than writing a coherent summary.

At a Glance

Impact Medium

Effort Moderate

Category Content

Primary Source

Google Search Central

How to Write Meta Descriptions

Content Medium Effort: Moderate

Provide a Dedicated Watch Page for Videos

Create a specific, dedicated landing page for individual videos to ensure they are eligible for rich video features in search results.

Why It Matters

For a video to be considered for maximum visibility (including Key Moments and the Video tab), Google requires it to be the primary focus of the page. If a video is merely complementary to a long article, it will not be indexed as a primary video result.

Key Principles

The primary intent of the watch page must be viewing the specific video.
The video cannot be hidden behind other elements or require complex interactions to load.
The page must have a unique title and description relevant to the video content.

Implementation

Specific, actionable steps to put this into practice.

Build a dedicated video gallery or resource section where each video has its own URL.
Ensure the video player is prominently placed above the fold and is not obscured.
Add video structured data (VideoObject) to the watch page to provide explicit metadata to crawlers.

Verification

How to confirm this practice is correctly implemented.

Use the Video Indexing report in Google Search Console to verify that the videos are recognized as the main content of their respective pages.
Check the URL Inspection tool to ensure the video container is present in the rendered HTML.
Validate the structured data using the Rich Results Test tool.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Expecting a video embedded at the bottom of a 2,000-word blog post to rank in the Video tab.
Using fragment identifiers (URL hashes) to load different videos on a single page.
Failing to provide a stable, accessible thumbnail URL for the video.

At a Glance

Impact Medium

Effort Moderate

Category Content

Primary Source

Google Search Central

Video SEO Best Practices

Content High Effort: Moderate

Update Content Before It Goes Stale

Freshness systems and AI search both favour recently updated content. Evergreen content left unchanged for more than a year is at structural risk of losing visibility to fresher competitors.

Why It Matters

Google's freshness systems show updated content when queries imply recency is relevant. Empirical research from Lily Ray's Tech SEO Connect 2025 presentation found that 50% of top-cited AI search content is less than 13 weeks old. Content that was comprehensive when published but has not been updated as the field evolved is no longer comprehensive. The strategic error is treating content as published-and-done; content is a living asset that requires maintenance to remain competitive.

Key Principles

High-traffic pages should be reviewed quarterly; all pages at minimum annually.
Content updates should be substantive, not cosmetic. Changing the publication date without updating content is ineffective and may be treated as a manipulative signal.
Updating a page with new information, recent statistics, and current examples is the most reliable way to renew its freshness signal.
Content recency is particularly important for rapidly evolving fields: technology, health, finance, and artificial intelligence.

Implementation

Specific, actionable steps to put this into practice.

Create a content maintenance calendar with review dates assigned to each published page based on how sensitive the topic is to change.
When updating content, document what changed and why; update the last-modified date and consider adding a "Last reviewed" note visible to readers.
Use Google Search Console's Performance data to identify pages with declining impressions; these are often the strongest candidates for a content refresh.

Verification

How to confirm this practice is correctly implemented.

Audit your content inventory quarterly for pages that have not been updated in more than 12 months and rank in positions 5-20 for commercially relevant queries.
Compare your content against the current top-ranking pages for your target queries. If competitors have more recent statistics or new sections you lack, update.
Monitor core algorithm update communications for any indication that freshness or content quality is a focus area of the update.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Changing only the publication date without updating the actual content.
Deleting outdated sections without replacing them with current information.
Treating all content as evergreen when some topics require quarterly review to remain accurate.

At a Glance

Impact High

Effort Moderate

Category Content

Primary Source

Lily Ray

Tech SEO Connect 2025: Empirical Research on AI Search

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Content Medium Effort: Moderate

Use Entity Disambiguation in Content

When your content references entities — people, organisations, places, products — that share names with other entities, use contextual signals to help Google's Knowledge Graph correctly identify which entity you mean. Ambiguity reduces confidence in entity association and weakens topical authority signals.

Why It Matters

Google's Knowledge Graph was built on the principle of "things, not strings." When Google encounters the word "Apple" in your content, it must determine whether you mean the technology company or the fruit. Contextual signals — surrounding words, co-occurring entities, structured data — help it make this determination with confidence. Bill Slawski's analysis of Google's entity-related patents demonstrates that Google assigns confidence scores to entity associations. Content that provides clear contextual signals for entity identification receives higher confidence scores, which strengthens the topical authority signal.

Key Principles

Use structured data (Schema.org) to explicitly declare entity types
Co-occur entities with their known associations (e.g., mention Tim Cook when writing about Apple Inc.)
Link to authoritative sources that confirm the entity's identity

Implementation

Specific, actionable steps to put this into practice.

Add full entity names on first reference in each piece of content
Implement appropriate Schema.org markup (Organisation, Person, Place, Product)
Add links to Wikipedia, official websites, or other authoritative sources for key entities
Use the Google Knowledge Graph Search API to verify that your entity is correctly identified

Verification

How to confirm this practice is correctly implemented.

Use the Google Rich Results Test to verify structured data implementation
Monitor entity-related queries in Search Console

Common Mistakes

Pitfalls and anti-patterns to avoid.

Implementing structured data without ensuring it matches the visible page content
Assuming Google will correctly identify entities without contextual signals

At a Glance

Impact Medium

Effort Moderate

Category Content

Primary Source

GOOGLE

Knowledge Graph API Documentation

Content Medium Effort: Moderate

Use Semantic Structure to Help Machines Parse Your Content

Clear semantic markup, logical heading hierarchy, descriptive section labels, and consistent content patterns help both Google's NLP systems and AI crawlers extract and represent your content accurately.

Why It Matters

Google's BERT and neural matching systems process semantic relationships between words and concepts, not just keyword presence. Content that is logically structured with clear headings, consistent terminology, and predictable patterns is easier for these systems to parse correctly. AI crawlers, as Lily Ray's research established, are particularly sensitive to structure: unstructured text makes them less effective whilst structured data enables complex reasoning. Investing in content architecture, not just content volume, produces dividends in both traditional and AI search.

Key Principles

Use a single H1 per page that clearly states the page's primary topic.
Structure content with a logical H2-H3 hierarchy that would function as a coherent document outline.
Use consistent terminology throughout a piece; synonym variation that aids human reading can confuse semantic matching systems.
Place the most important information close to the top of the page; both crawlers and readers benefit from front-loaded content.

Implementation

Specific, actionable steps to put this into practice.

Audit your content structure using a heading extraction tool; the heading outline should make sense as a standalone document outline without the body text.
Use descriptive heading text that contains the primary concept of that section, not creative labels that require the body text to be meaningful.
Add FAQ sections or structured question-and-answer patterns to content where the topic supports it; these map to structured data opportunities and voice search matching.

Verification

How to confirm this practice is correctly implemented.

Extract only the headings from a page and read them in sequence. Do they communicate the content structure clearly without the body text?
Use Google Search Console URL Inspection to view the rendered page and check whether Google is parsing the content structure as intended.
Test whether your content is eligible for featured snippet extraction; well-structured content with direct answers is the primary source of featured snippets.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using heading tags (H2, H3) for visual formatting rather than semantic structure.
Varying terminology for the same concept throughout an article to avoid repetition; this undermines semantic matching.
Burying the most important conclusion or direct answer at the end of a long article rather than leading with it.

At a Glance

Impact Medium

Effort Moderate

Category Content

Primary Source

Google Search Central

A Guide to Google Search Ranking Systems

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Content High Effort: Easy

Write Distinct and Descriptive Title Tags

Create unique, concise, and descriptive title tags for every page to clearly communicate the page's value to both users and search engines.

Why It Matters

The title link is often the primary piece of information people use to decide which result to click. Vague, duplicated, or keyword-stuffed titles confuse users and can lead Google to automatically rewrite the title link in search results.

Key Principles

Every page must have a unique title specified in the <title> element.
Titles should be descriptive and concise, avoiding vague terms like 'Home' or 'Profile'.
Boilerplate text that repeats across many pages diminishes the title's value.

Implementation

Specific, actionable steps to put this into practice.

Audit the site to ensure every page has a populated <title> element.
Write titles that accurately reflect the specific content of the page, placing the most important keywords near the beginning.
Brand your titles concisely by appending the site name at the end, separated by a delimiter (e.g., ' - SiteName').

Verification

How to confirm this practice is correctly implemented.

Crawl the site with a tool like Screaming Frog to identify missing, duplicate, or overly long title tags.
Perform a site: search in Google to see how the titles are actually being rendered in the SERPs.
Check Google Search Console for any HTML improvement suggestions related to title tags.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using the exact same title tag for multiple pages, making them indistinguishable in search results.
Keyword stuffing (e.g., 'Cheap Shoes, Buy Shoes, Best Shoes'), which looks spammy and harms click-through rates.
Writing excessively long titles that get truncated, hiding the most critical information.

At a Glance

Impact High

Effort Easy

Category Content

Primary Source

Google Search Central

Influencing Title Links in Google Search

Fundamentals High Effort: Easy

Avoid Hidden Text and Link Abuse

Ensure all text and links intended for search engines are clearly visible to human users, avoiding manipulative CSS or HTML techniques.

Why It Matters

Placing content on a page solely to manipulate search engines while hiding it from users is a direct violation of Google's spam policies. This practice, known as cloaking or hidden text abuse, can result in manual actions and complete removal from search results.

Key Principles

Content must be presented identically to both search engine crawlers and human visitors.
Dynamic elements like accordions or tabs that require user interaction are acceptable, provided the content is accessible.
Text intended only for screen readers is permitted if its purpose is accessibility, not manipulation.

Implementation

Specific, actionable steps to put this into practice.

Review page templates to ensure no text is styled to blend into the background (e.g., white text on a white background).
Ensure links are clearly identifiable and not hidden within single characters or punctuation marks.
Use standard HTML and CSS for dynamic content presentation without relying on off-screen positioning for SEO text.

Verification

How to confirm this practice is correctly implemented.

Disable CSS in the browser to view the raw HTML content and check for unexpected blocks of text.
Use the URL Inspection Tool in Search Console to view the rendered HTML and ensure it matches the user experience.
Conduct manual reviews of page source code for suspicious inline styles or hidden divs.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Setting font sizes to zero or opacity to zero to hide keyword-rich paragraphs.
Using CSS to position text thousands of pixels off-screen.
Hiding a backlink by linking a hyphen or a tiny, unnoticeable image.

At a Glance

Impact High

Effort Easy

Category Fundamentals

Primary Source

Google Search Central

Spam Policies for Google Web Search

Fundamentals High Effort: Moderate

Avoid Intrusive Interstitials on Mobile

Ensure that the main content of a page is immediately accessible to users transitioning from mobile search results, without being obscured by intrusive pop-ups.

Why It Matters

Pages that show intrusive interstitials provide a poor user experience because they block the content the user expected to see. Google uses the accessibility of main content on mobile devices as a ranking signal, and pages that obscure content upon entry may rank lower.

Key Principles

Content must be easily accessible immediately after a user taps a search result.
Pop-ups that cover the main content or require dismissal before reading are considered intrusive.
Legally required interstitials (like cookie consent or age verification) are exempt from this penalty.

Implementation

Specific, actionable steps to put this into practice.

Replace full-screen promotional pop-ups with banners that use a reasonable amount of screen space and are easily dismissible.
Delay the triggering of non-essential pop-ups until the user has engaged with the content (e.g., scrolled halfway down the page).
Ensure that any login dialogs are only used for content that is genuinely private or behind a paywall, not for publicly indexable articles.

Verification

How to confirm this practice is correctly implemented.

Test the mobile experience manually using a physical device to ensure no pop-ups block the initial view.
Use Chrome DevTools device mode to simulate the mobile viewport and verify banner sizing.
Review Google Search Console's Page Experience report for any mobile usability warnings.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Displaying a standalone interstitial that forces the user to find a tiny 'close' button before accessing the page.
Using a layout where the above-the-fold portion looks like an interstitial, pushing the actual content below the fold.
Triggering an email signup pop-up immediately upon page load for users arriving from organic search.

At a Glance

Impact High

Effort Moderate

Category Fundamentals

Primary Source

Google Search Central

Helping users easily access content on mobile

Fundamentals High Effort: Moderate

Canonicalise Every URL Decisively

Every page should have exactly one canonical URL. Failing to declare this invites Google to make the decision for you, and it may not choose the version you prefer.

Why It Matters

URL proliferation is silent. Tracking parameters, session identifiers, trailing slashes, HTTP versus HTTPS variants, www versus non-www — each combination creates a potential duplicate. Without canonical declarations, crawl budget splits across variants, link equity dilutes, and ranking signals fragment. Canonicalisation is not a fix for problems; it is the declaration of intent that prevents them from occurring in the first place.

Key Principles

Every indexable page should carry a self-referencing canonical tag pointing to its own preferred URL.
Canonical tags signal to Google which URL should consolidate ranking signals and appear in search results.
Canonical decisions should be made at the architectural level, not applied reactively after indexation problems appear.
Sitemaps should list only canonical URLs; including non-canonical variants wastes crawl resource and creates conflicting signals.

Implementation

Specific, actionable steps to put this into practice.

Add a self-referencing canonical meta tag to every page template so new pages receive it automatically on publication.
Implement server-level redirects from all URL variants (HTTP, www, trailing slash) to the single canonical version before the canonical tag layer is applied.
Review parameterised URLs generated by filtering, sorting, or session management systems and ensure they carry canonicals pointing to the clean base URL.

Verification

How to confirm this practice is correctly implemented.

Crawl the site using Screaming Frog and export the canonical report. Every page should show a canonical pointing to itself or its preferred variant.
Use Google Search Console URL Inspection to verify that Google agrees with your declared canonical. When GSC shows a different Google-selected canonical, investigate why.
Check that your sitemap contains only canonical URLs by cross-referencing against the canonical report from your crawler.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Forgetting to add canonical tags to new page templates, so new content publishes without them.
Using canonical tags to consolidate pages with substantially different content, which Google will typically override.
Setting conflicting canonical signals: a canonical tag pointing one way while a hreflang or sitemap entry points another.

At a Glance

Impact High

Effort Moderate

Category Fundamentals

Primary Source

Google Search Central

Google SEO Starter Guide: Fundamentals

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Fundamentals High Effort: Moderate

Conduct Regular Technical SEO Audits

A technical SEO audit is a systematic review of the factors that affect how search engines crawl, index, and rank a website. Sites that are not audited regularly accumulate technical debt — broken redirects, orphan pages, crawl errors — that compounds over time and suppresses rankings.

Why It Matters

John Mueller has stated in multiple Google Search Central office hours that technical issues are a common cause of ranking underperformance that site owners are unaware of. Crawl errors, broken internal links, duplicate content, and misconfigured robots.txt files can all suppress rankings without triggering any explicit notification. Google's documentation on Search Console explicitly frames it as a monitoring tool: "Search Console helps you monitor your site's performance in Google Search and troubleshoot issues." But Search Console only surfaces issues that Google has detected — a regular crawl-based audit catches issues before Google does.

Key Principles

A full crawl should be the foundation of every audit
Audit findings should be prioritised by impact: errors before warnings, high-traffic pages before low-traffic pages
Audit findings should be tracked and resolved systematically, not ad hoc

Implementation

Specific, actionable steps to put this into practice.

Review the following in every audit: broken links (4xx errors), redirect chains, duplicate title tags, missing meta descriptions, orphan pages, pages blocked by robots.txt, pages with noindex, Core Web Vitals status, structured data errors
Cross-reference crawl findings with Search Console data
Prioritise findings by traffic impact and fix severity
Document findings and resolutions in a running audit log

Verification

How to confirm this practice is correctly implemented.

Verify that previously identified issues have been resolved
Cross-reference with Search Console Index Coverage report

Common Mistakes

Pitfalls and anti-patterns to avoid.

Crawling only a sample of the site rather than the full URL inventory
Identifying issues without prioritising or tracking resolution
Treating a technical audit as a one-time project rather than a recurring process

At a Glance

Impact High

Effort Moderate

Category Fundamentals

Primary Source

GOOGLE SEARCH CENTRAL

Search Console Help — Monitoring and Debugging

Fundamentals High Effort: Easy

Design for People, Not Algorithms

Google's ranking systems are engineered to reward content created for people. Optimising for the algorithm instead of the reader is working against what Google is actively trying to surface above you.

Why It Matters

The most durable misconception in SEO is that optimising for Google and optimising for users are different activities. Google has spent two decades and billions of dollars trying to make these identical. If you are writing for rankings, you are working against that effort. People-first content earns better engagement signals, attracts better links, and survives algorithm updates that destroy search-engine-first content. Google's own guidance is unambiguous: automated ranking systems are designed to prioritise helpful, reliable information created to benefit people, not to manipulate rankings.

Key Principles

Content must be created primarily to benefit the reader, not to achieve a ranking.
Ask whether the content demonstrates genuine depth that goes beyond obvious information already available elsewhere.
Content created around a search term without real user value is search-engine-first content, regardless of how it is packaged.
Google's automated systems are trained to identify and reward people-first content and demote content built primarily for rankings.

Implementation

Specific, actionable steps to put this into practice.

Evaluate each piece of content against this question: "Would this content exist if search engines did not?" If the honest answer is no, reconsider the brief.
Use a self-assessment checklist before publishing: Does the content provide original insight? Is it clearly written by someone with genuine knowledge? Does it leave the reader better informed than before?
When creating content for a competitive query, focus on what the reader genuinely needs to know rather than what you believe you need to include to rank.

Verification

How to confirm this practice is correctly implemented.

Read the content as the target reader. Does it answer the question completely without unnecessary padding or filler?
Check whether the content provides anything beyond what the top-ranking pages already say.
Ask a trusted colleague who is not involved in SEO whether the content is genuinely useful and worth sharing.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Publishing content solely because a keyword has search volume, without genuine expertise or value to add.
Adding padding to reach a word count target rather than writing to the depth the topic actually requires.
Using AI to generate content at scale without human editorial review for accuracy and genuine added value.

At a Glance

Impact High

Effort Easy

Category Fundamentals

Primary Source

Google Search Central

A Guide to Google Search Ranking Systems

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Fundamentals Medium Effort: Easy

Optimise at the Page Level, Not the Site Level

Google ranks individual pages, not websites. A strong domain does not protect weak pages, and a weak domain does not prevent strong pages from ranking.

Why It Matters

Site-level thinking produces site-level work. Improving 'the site' is meaningless without specifying which pages are being improved and why. Google's ranking systems evaluate individual pages against individual queries. Strong site-wide signals contribute to but do not override page-level quality signals. A high-authority domain with thin, poorly structured pages will lose to a lower-authority domain with excellent, well-structured pages on those specific queries. Google's Ranking Systems Guide is explicit: ranking is designed to work at the page level.

Key Principles

Ranking improvements require page-level diagnosis and page-level action.
Each page must individually satisfy E-E-A-T criteria; site-wide authority does not transfer automatically.
Quality and relevance signals are evaluated per page, not averaged across the domain.
A page that does not serve search intent cannot be saved by domain authority alone.

Implementation

Specific, actionable steps to put this into practice.

Audit underperforming pages individually rather than applying site-wide changes and waiting to see which pages respond.
For each target page, identify the specific ranking system most relevant to its performance: freshness, link analysis, content quality, or semantic matching.
Prioritise page-level improvements by traffic opportunity: pages ranking in positions 5-20 for commercially relevant queries have the highest marginal return on improvement effort.

Verification

How to confirm this practice is correctly implemented.

Use Google Search Console's Pages report to identify individual page performance rather than relying solely on domain-level metrics.
When making improvements, document which pages were changed and track their performance independently to isolate the effect of the changes.
Compare underperforming pages against top-ranking competitors at the page level, not the domain level.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Running site-wide audits and prioritising fixes by volume rather than per-page traffic opportunity.
Assuming that improving overall domain authority will automatically lift all pages.
Neglecting individual pages because 'the domain is strong enough.'

At a Glance

Impact Medium

Effort Easy

Category Fundamentals

Primary Source

Google Search Central

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Fundamentals Medium Effort: Easy

Set Realistic Timelines for SEO Results

SEO changes take weeks to months to produce visible results. Expecting fast returns leads to premature decisions that undo work before it has had time to show impact.

Why It Matters

The gap between implementing an SEO change and observing its impact in rankings or traffic is rarely less than four weeks and often extends to three to six months. This lag is structural: Googlebot must recrawl the page, process the change, update its index, and re-evaluate rankings. Changes that appear not to have worked after two weeks may simply not have been given time to work. Google's own starter guide acknowledges this: not all changes produce noticeable impact, and iteration and testing are necessary. The misjudgement is rampant; it produces a cycle of constant tactical switching that prevents any single initiative from producing measurable results.

Key Principles

Most SEO changes require four to twelve weeks to show ranking impact; content and link changes often take longer.
Attribution is difficult; multiple changes made simultaneously cannot be reliably separated in their effects.
Not all changes produce noticeable results, but that does not mean the practice is wrong.
Iteration requires patience: change, observe, wait, interpret, then adjust.

Implementation

Specific, actionable steps to put this into practice.

When implementing SEO changes, record the change date and the specific pages affected in a changelog.
Set explicit review milestones at four weeks, eight weeks, and twelve weeks for each change batch.
Make one category of change at a time where possible (technical, content, links) to improve attribution accuracy.

Verification

How to confirm this practice is correctly implemented.

Review Google Search Console's Performance data at four-week intervals after each change, comparing to the equivalent period in the prior year.
Use Looker Studio or similar to create a timeline view that overlays change dates against impressions and click data for the specific pages affected.
Assess whether rankings are trending in the right direction before concluding a change has not worked.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Reverting changes after two weeks because no result is visible, then losing any benefit that would have accrued over the full assessment period.
Making multiple significant changes simultaneously, then being unable to determine what drove any observed improvement or decline.
Setting client or stakeholder expectations that create pressure to show results within timelines that are structurally impossible for SEO to meet.

At a Glance

Impact Medium

Effort Easy

Category Fundamentals

Primary Source

Google Search Central

Google SEO Starter Guide: Fundamentals

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Fundamentals High Effort: Moderate

Understand and Respond to Manual Actions

A manual action is a documented, human-applied penalty for a specific spam policy violation. It is distinct from an algorithmic demotion. It requires a specific remediation process — not a general content improvement programme — followed by a formal reconsideration request.

Why It Matters

Google's manual actions documentation describes the process precisely: "A manual action is applied when a human reviewer at Google has determined that pages on your site are not compliant with Google's webmaster quality guidelines." The consequence can range from a partial demotion of specific pages to complete removal from search results. The critical distinction — which John Mueller has emphasised repeatedly — is that a manual action is always visible in Google Search Console's Manual Actions report. If you do not have a manual action listed there, you do not have a manual action. A traffic drop is not evidence of a manual action.

Key Principles

The remediation must address the specific violation described, not general SEO improvement
Reconsideration requests must document what was found and what was fixed
Recovery after a successful reconsideration request can take weeks

Implementation

Specific, actionable steps to put this into practice.

If a manual action is present, read the description carefully to identify the specific violation
Fix the violation completely — partial fixes result in denied reconsideration requests
Document every step of the remediation process
Submit a reconsideration request through Search Console with full documentation
If the request is denied, review the reason, make additional fixes, and resubmit

Verification

How to confirm this practice is correctly implemented.

Monitor organic traffic for 4-8 weeks following manual action removal

Common Mistakes

Pitfalls and anti-patterns to avoid.

Confusing an algorithmic demotion with a manual action
Making general content improvements instead of addressing the specific violation
Failing to document the remediation process in the reconsideration request

At a Glance

Impact High

Effort Moderate

Category Fundamentals

Primary Source

GOOGLE SEARCH CENTRAL

Manual Actions Report

Links High Effort: Hard

Build Topical Authority Through Content Clusters

A site that covers a topic comprehensively — with a main pillar page and multiple supporting cluster pages — signals deeper topical authority than a site with a single page on the same topic, regardless of that page's quality.

Why It Matters

Google's Quality Rater Guidelines assess expertise and authoritativeness at the site level, not just the page level. A site that has published extensively on a topic — covering the main concept, its subtopics, its applications, its controversies, and its history — demonstrates a depth of engagement that a single page cannot replicate. Rand Fishkin's research at Moz demonstrated that sites with comprehensive topic coverage consistently outranked sites with single, high-quality pages on the same topic for competitive queries. The mechanism is both direct (more pages means more entry points for long-tail queries) and indirect (comprehensive coverage earns more links from other sites that reference specific aspects of the topic).

Key Principles

Each cluster page covers one subtopic in depth and links back to the pillar
All cluster pages link to each other where relevant
The cluster should collectively answer every significant question a user might have about the topic

Implementation

Specific, actionable steps to put this into practice.

Create or designate a pillar page that provides a comprehensive overview
Create individual cluster pages for each subtopic
Build bidirectional internal links between the pillar and all cluster pages
Identify gaps in the cluster by monitoring which queries trigger your pillar page in Search Console but do not have a dedicated cluster page

Verification

How to confirm this practice is correctly implemented.

Monitor the pillar page's ranking for head terms over 90 days following cluster completion
Check that all cluster pages are indexed and appearing in search results

Common Mistakes

Pitfalls and anti-patterns to avoid.

Failing to link cluster pages back to the pillar
Building clusters around keyword categories rather than genuine user intent
Treating the cluster as a one-time project rather than an ongoing content programme

At a Glance

Impact High

Effort Hard

Category Links

Primary Source

GOOGLE

Search Quality Rater Guidelines

Links High Effort: Moderate

Build Topical Authority Through Strategic Internal Linking Clusters

Topical authority is built by covering a subject comprehensively and linking related content together. It signals expertise to search engines across an entire subject area.

Why It Matters

Search engines evaluate entities and topics, not just isolated keywords. By grouping related content into clusters and linking them together, you signal to Google the breadth and depth of your expertise. A strong internal linking structure distributes PageRank from high-authority pages to deeper content and establishes a semantic relationship between pages, lifting the ranking potential of the entire cluster.

Key Principles

Organise content into topic clusters, consisting of a broad pillar page and specific, detailed cluster pages.
Every cluster page must link back to the central pillar page.
The pillar page should link out to all the relevant cluster pages.

Implementation

Specific, actionable steps to put this into practice.

Use keyword-rich, descriptive anchor text for internal links, providing clear context about the destination page.
Ensure links are placed contextually within the body of the content, not just relegated to navigation menus or footers.
Integrate internal links naturally where they provide value to the reader s journey, rather than placing them above the fold as a navigational device.

Verification

How to confirm this practice is correctly implemented.

Use crawling tools to visualise your site architecture and ensure topic clusters are tightly interlinked without orphaned pages.
Monitor rankings for the entire cluster of keywords; successful implementation usually results in a collective lift across related terms.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using generic anchor text like click here or read more for internal links.
Creating comprehensive content but failing to link it to the rest of the site, leaving it orphaned and undiscoverable by crawlers.

At a Glance

Impact High

Effort Moderate

Category Links

Primary Source

Google Search Central

Link Best Practices

Links High Effort: Moderate

Disavow Toxic Links Correctly and Conservatively

The disavow tool should be used only for links you are certain are harmful and that you cannot have removed manually. Indiscriminate disavowal can remove legitimate link equity.

Why It Matters

Google's disavow documentation is explicit that the tool is intended for "unnatural links that you can't get removed." It is not a general-purpose link cleaning tool. Disavowing legitimate links — even low-quality ones — removes real PageRank from your profile. The risk of over-disavowal is as real as the risk of under-disavowal. The appropriate use case is narrow: links that were purchased or built through link schemes, links from sites that exist solely to sell links, and links that have triggered or are likely to trigger a manual action. For all other links, Google's systems are capable of ignoring low-quality links without manual intervention.

Key Principles

Disavow at the domain level only when the entire domain is problematic
Disavow at the URL level for isolated pages on otherwise legitimate domains
Document every disavowal decision with the reason

Implementation

Specific, actionable steps to put this into practice.

Identify links that match the criteria for disavowal: purchased links, link scheme participants, or sites with manual actions
Attempt to contact the linking site and request removal — document every attempt
For links that cannot be removed, add them to a disavow file in the correct format
Submit the disavow file through Google Search Console
Review and update the disavow file quarterly

Verification

How to confirm this practice is correctly implemented.

Monitor organic traffic trends for 8-12 weeks following submission
Verify the disavow file format using Google's documentation before submission

Common Mistakes

Pitfalls and anti-patterns to avoid.

Disavowing entire domains when only specific pages are problematic
Failing to attempt manual removal before disavowal
Using the disavow tool as a first response to a traffic drop (it is not a recovery tool for algorithmic issues)

At a Glance

Impact High

Effort Moderate

Category Links

Primary Source

GOOGLE SEARCH CENTRAL

Disavow Backlinks to Your Site

Links High Effort: Hard

Earn Links Through Original Research and Data

Original data — surveys, studies, proprietary analyses — earns links passively because it becomes a primary source that other publishers must cite. This is the most sustainable link acquisition strategy available.

Why It Matters

Google's link best practices documentation makes clear that links should be earned, not manufactured. The most reliable way to earn links at scale is to produce content that other publishers need to reference. Original research, unique datasets, and proprietary analyses create this dependency. A study that reveals a counterintuitive finding in your industry will attract links from journalists, bloggers, and practitioners for years after publication. No other content type generates this compounding return. Rand Fishkin's empirical research at SparkToro consistently demonstrates that data-driven content earns links at 3-5x the rate of equivalent opinion or how-to content.

Key Principles

The methodology must be transparent and reproducible to establish credibility
The finding must be counterintuitive or surprising to generate media interest
The content must be easy to cite — clear headline statistics, embeddable charts, and a citable URL

Implementation

Specific, actionable steps to put this into practice.

Design a methodology: survey, analysis of proprietary data, scraping of public records, or original testing
Publish the findings with a clear, citable headline statistic and supporting detail
Distribute to journalists and bloggers who cover your industry with a personalised outreach email
Create an embeddable version of the key chart or data visualisation

Verification

How to confirm this practice is correctly implemented.

Track the number of citations in Google News for your study's headline finding
Set up Google Alerts for the study's title and key statistic

Common Mistakes

Pitfalls and anti-patterns to avoid.

Publishing findings without a clear, quotable headline statistic
Failing to promote the research to journalists — publishing alone is insufficient
Repackaging publicly available data as "original research"

At a Glance

Impact High

Effort Hard

Category Links

Primary Source

GOOGLE SEARCH CENTRAL

Links High Effort: Easy

Ensure Every Important Page Has at Least One Internal Link

A page with no internal links pointing to it is functionally invisible to crawlers and receives no PageRank from the internal link graph. Google's own guidance is explicit: every page you care about should have at least one internal link from another page.

Why It Matters

Internal links are how PageRank flows through a site. Pages that are not linked internally exist in isolation; they depend entirely on external links or direct URL discovery for any traffic. Orphan pages are one of the most common and most avoidable technical SEO failures. They are created every time content is published without being integrated into the site's existing internal link structure, which is the norm on sites without an explicit internal linking process.

Key Principles

Every published page should have at least one editorial internal link from a topically related page.
The most important pages should receive the most internal links, proportional to their commercial or editorial importance.
Internal links should use descriptive anchor text that reflects the destination page topic.
Deep pages (more than three clicks from the homepage) are underserved by the internal link graph and need deliberate attention.

Implementation

Specific, actionable steps to put this into practice.

After publishing any new page, add at least one internal link to it from an existing related page before the publishing session ends.
Run a site crawl monthly and filter for pages with zero inbound internal links; these are orphan pages requiring immediate attention.
Create a linking template for new content types: every blog post links to two related posts; every product page links to its category and two related products.

Verification

How to confirm this practice is correctly implemented.

Crawl the site and export the inbound link count for each URL. Filter for pages with zero inbound internal links.
Check whether your highest-priority commercial pages are receiving internal links from contextually relevant content pages, not only from navigation menus.
Use Google Search Console's Internal Links report to identify which pages receive the most internal link equity.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Publishing new content without updating any existing pages to link to it.
Relying on navigation menus and footers as the sole source of internal links to important pages.
Treating the internal link audit as a one-time exercise rather than an ongoing part of the content publishing process.

At a Glance

Impact High

Effort Easy

Category Links

Primary Source

Google Search Central

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Links Medium Effort: Easy

Link to External Sources to Establish Credibility

Citing and linking to external authoritative sources demonstrates transparency and trustworthiness. Google's guidance is clear: using external links helps establish credibility and is not something to avoid.

Why It Matters

Many practitioners avoid external links from a misguided concern that they 'lose PageRank.' This concern is outdated in its practical application. Google explicitly states that linking to authoritative external sources helps establish a site's trustworthiness. Content that makes factual claims without citations is harder to trust than content that points readers to its sources. The self-contained, no-outbound-links content strategy is a 2005 SEO habit that should have been retired a decade ago.

Key Principles

Cite primary sources (original research, official documentation, expert publications) rather than secondary sources such as articles about the research.
External links to authoritative sources reinforce the credibility of claims made in the content.
Use standard, non-qualified links for editorial external references; reserve nofollow for links you genuinely do not trust.
Opening external links in a new tab is a UX convention that reduces exit risk without affecting link signals.

Implementation

Specific, actionable steps to put this into practice.

Establish a citation practice for all published content: every factual claim requires either a linked source or a clear attribution.
Prioritise linking to .gov sources, .edu institutions, published academic research, and official documentation as primary references.
When updating content, verify that all external links still resolve and point to the original, current source rather than having redirected to irrelevant destinations.

Verification

How to confirm this practice is correctly implemented.

Audit external links periodically for broken links (4xx responses) and redirects that have changed destination since the link was placed.
Check whether your content cites primary sources or intermediary articles; swap secondary citations for primary source links where possible.
Review whether high-stakes claims (health, finance, safety) are supported by linked, authoritative citations.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Applying nofollow to all external links as a blanket policy when most external links to authoritative sources require no qualification at all.
Citing secondary sources (news articles about a study) instead of the original published research.
Not checking external links periodically, allowing broken or redirected citations to accumulate.

At a Glance

Impact Medium

Effort Easy

Category Links

Primary Source

Google Search Central

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Links Medium Effort: Easy

Use Link Qualification Attributes Correctly

The rel='nofollow', rel='sponsored', and rel='ugc' attributes communicate link intent to Google. Using them incorrectly — or not at all where required — sends misleading signals and may constitute a violation of Google's spam policies.

Why It Matters

Link qualification attributes exist because not all links represent editorial endorsement. Paid links without the sponsored attribute pass PageRank in a way Google considers manipulative. User-generated content links without the ugc attribute may be trusted by Google when the site owner has no control over the destination. Nofollow, when applied indiscriminately to all external links, reduces its effectiveness as a signal for genuinely untrusted links. Getting this taxonomy right protects the site from link scheme violations and helps Google understand the actual link landscape.

Key Principles

rel='sponsored' is required for all paid links, affiliate links, and advertorial links.
rel='ugc' should be used for links in user-generated content areas (comments, forums, reviews) where the site owner does not editorially control the linked destination.
rel='nofollow' should be used only for links the site owner does not vouch for, not as a blanket policy for all external links.
Standard editorial links to external authoritative sources require no qualification attribute.

Implementation

Specific, actionable steps to put this into practice.

Audit all affiliate and advertising partnerships to confirm that the relevant links carry rel='sponsored' attributes.
Configure comment and user review systems to automatically apply rel='ugc' to all links in user-submitted content.
Review the use of rel='nofollow' sitewide and remove it from editorial links to authoritative external sources where it was applied as a blanket policy.

Verification

How to confirm this practice is correctly implemented.

Crawl the site and extract all links with their rel attribute values. Identify any pattern of sponsored or ugc links without the appropriate attribute.
Check your affiliate integration documentation to confirm that the link implementation meets Google's sponsored attribute requirement.
Verify that your comment system configuration is applying ugc to all user-submitted links automatically.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using rel='nofollow' on all external links as a precaution, which obscures the genuine signal for links you genuinely do not trust.
Failing to add rel='sponsored' to affiliate product links, which Google may treat as a link scheme violation.
Not configuring ugc on comment or forum link systems, leaving user-generated links as unqualified editorial signals.

At a Glance

Impact Medium

Effort Easy

Category Links

Primary Source

Google Search Central

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Links High Effort: Easy

Write Descriptive Anchor Text for Every Link

Anchor text is the primary signal to both users and search engines about where a link leads. Generic phrases like 'click here' or 'read more' communicate nothing about the destination page.

Why It Matters

Google uses anchor text as a relevance signal for the linked page. When multiple pages link to the same destination using descriptive anchor text, Google forms a clearer picture of what that page is about. Poor anchor text creates noise in this signal. Google's own guidance is unambiguous: 'Good anchor text is descriptive, reasonably concise, and relevant to the page that it's on and to the page it links to.' A further test from the same source: try reading only the anchor text out of context and check if it's specific enough to make sense by itself.

Key Principles

Anchor text should make sense when read in isolation, out of context from the surrounding sentence.
Descriptive anchors should not be excessively long or keyword-stuffed; natural language that communicates the destination is sufficient.
Each link anchor should provide new information about the destination, not repeat what is already obvious from the surrounding paragraph.
Image links should have descriptive alt text that functions as anchor text for the linked destination.

Implementation

Specific, actionable steps to put this into practice.

When writing or editing internal links, read the anchor text in isolation and ask whether it clearly communicates the destination page's topic.
Audit existing content for generic anchor text using a site crawl tool and update the worst offenders, prioritising your highest-traffic pages.
Create an anchor text style guide for editorial teams that specifies what constitutes descriptive versus generic anchor text with clear examples.

Verification

How to confirm this practice is correctly implemented.

Export internal links from a site crawl and filter for anchors containing only 'click here,' 'here,' 'read more,' 'this,' 'link,' or similar generic phrases.
Test anchor text in isolation: cover the surrounding sentence and check whether the anchor alone communicates the linked page topic.
Review whether internal links use natural language anchors or keyword-optimised anchors; the latter creates an over-optimisation risk.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using 'click here' or 'read more' as anchor text because it makes sense in context — it makes sense to the reader but not to Google.
Keyword-stuffing anchor text beyond what reads naturally in context, which can trigger over-optimisation signals.
Using the full URL as visible anchor text when the page has a title that better communicates its content.

At a Glance

Impact High

Effort Easy

Category Links

Primary Source

Google Search Central

Tech SEO Connect 2025: Empirical Research on AI Search

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Technical High Effort: Moderate

Add Structured Data Before the Page Goes Live

Structured data must be present at a page's first crawl. AI crawlers and Googlebot both form context from the first version of a page they retrieve; retrofitting structured data later may not update cached interpretations.

Why It Matters

Empirical research from Lily Ray's Tech SEO Connect 2025 presentation found that structured data must be present at the first touchpoint to be effective for AI crawlers. Context bias is real: if a bot retrieves unstructured content first, it may ignore subsequently structured content in the same session or subsequent crawls. The actionable mandate is not to release pages without structured data. For Google's standard indexing, structured data enables rich results and helps the Knowledge Graph understand entity relationships. Retrofitting it after publication is better than not adding it at all, but the first-publish discipline avoids the problem entirely.

Key Principles

Structured data should be implemented in JSON-LD format and validated before any page is published.
The appropriate schema type must match the content on the page: Article for editorial, Product for commerce, FAQ for question-and-answer, and so on.
All required properties for each schema type must be present for rich result eligibility.
Structured data must reflect visible on-page content; marking up information not present on the page violates Google's webmaster guidelines.

Implementation

Specific, actionable steps to put this into practice.

Add structured data generation to your CMS page templates so every new page receives the appropriate schema automatically based on its content type.
Validate structured data using Google's Rich Results Test before publishing any new content type or template.
Set up a pre-publication checklist that includes structured data validation as a mandatory step, not an optional review.

Verification

How to confirm this practice is correctly implemented.

Run the Rich Results Test on all key page types quarterly and after any template change.
Review Google Search Console's Enhancements report to monitor rich result eligibility and identify any structured data errors across the site.
Use Screaming Frog's structured data extraction mode to audit schema coverage across all pages in the site.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Implementing structured data after a page has already been indexed and expecting immediate rich result eligibility.
Using structured data types that do not match the page content (marking a blog post as a Product schema, for example).
Including structured data in the template but hardcoding values that become stale as content changes over time.

At a Glance

Impact High

Effort Moderate

Category Technical

Primary Source

Lily Ray

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Technical High Effort: Easy

Avoid Soft 404 Errors and Manage HTTP Status Codes

A soft 404 returns a 200 OK status but shows a not-found or empty page. Googlebot treats these as real pages and keeps crawling them, wasting budget and polluting the index.

Why It Matters

Proper HTTP status codes are how servers communicate with search engine crawlers. If a page is gone, returning a 200 OK status confuses Googlebot. It forces Google to spend crawl budget analysing a useless page and can lead to the page remaining in the index, providing a poor user experience. Explicitly managing status codes ensures Google understands your site s inventory accurately.

Key Principles

Pages that no longer exist and have no equivalent replacement must return a 404 (Not Found) or 410 (Gone) status code.
Pages that have moved permanently must use a 301 (Moved Permanently) redirect to the exact new location.
Never redirect deleted pages en masse to the homepage; Google treats this as a soft 404.

Implementation

Specific, actionable steps to put this into practice.

Configure your server or CMS to return a hard 404 HTTP header alongside your custom, user-friendly 404 error page.
If a product is temporarily out of stock, do not return a 404; keep the page live with a 200 status and clearly state the availability.
Regularly audit your site for broken links and update them to point to the correct, live URLs.

Verification

How to confirm this practice is correctly implemented.

Monitor the Page Indexing report in Google Search Console specifically for the Soft 404 error category.
Use server log analysis or crawling tools to verify the exact HTTP headers being returned by your URLs.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Redirecting all 404 errors to the homepage to preserve link equity, which frustrates users and confuses search engines.
Displaying a custom 404 design but failing to configure the server to actually send the 404 HTTP header.

At a Glance

Impact High

Effort Easy

Category Technical

Primary Source

Google Search Central

HTTP Status Codes and Network Errors

Technical Medium Effort: Easy

Build URLs That Humans Can Read

URLs should communicate page content to both users and search engines. Opaque, parameter-heavy, or auto-generated URLs undermine crawlability and user trust.

Why It Matters

A URL is the first signal a user receives about a page's relevance before clicking. It is also a significant signal Googlebot uses to understand page content and priority. Empirical research from Lily Ray's Tech SEO Connect 2025 presentation found that natural language URLs of 5-7 words drove 11.4% more AI search citations than opaque alternatives. The habit of auto-generating URLs from database IDs or CMS systems without editorial review is one of the most persistent avoidable failures in technical SEO.

Key Principles

URLs should contain meaningful words that describe the page content without requiring the page to be opened.
Shorter, cleaner URL structures are preferable to long, parameter-heavy ones.
URL structure should reflect site architecture logically, helping both users and crawlers understand content relationships.
Avoid unnecessary parameters, session identifiers, and auto-generated numeric IDs in publicly indexed URLs.

Implementation

Specific, actionable steps to put this into practice.

Define URL structure conventions for each content type during site architecture design, before content is created.
Configure your CMS to generate slugs from titles but provide an editorial override field so authors can shorten or clarify slugs before publishing.
For existing sites with poor URL structure, create a URL migration plan with proper 301 redirects before making changes. Never change URLs without redirects.

Verification

How to confirm this practice is correctly implemented.

Read your URLs aloud. If they do not communicate the page topic without needing to open the page, they need improvement.
Crawl your site and filter for URLs containing query parameters, session IDs, or numeric-only path segments that could be cleaned up.
Check Google Search Console's URL breadcrumb data to see how Google is interpreting your URL structure in search results.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Changing URL structures on established pages without implementing 301 redirects, destroying accumulated ranking history.
Allowing URL parameters to generate thousands of indexable duplicate pages via pagination, filtering, or sorting.
Including dates in URLs for evergreen content, creating false freshness signals and complicating URL management over time.

At a Glance

Impact Medium

Effort Easy

Category Technical

Primary Source

Google Search Central

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Technical High Effort: Easy

Configure robots.txt Conservatively and Test Before Deploying

A correctly configured robots.txt file is a narrow set of specific exclusions. Broad Disallow rules are the most common source of self-inflicted indexation failure.

Why It Matters

Robots.txt errors are among the most impactful and hardest to notice. A single Disallow: / directive locks an entire site out of Google's index with no error message, no warning, and no alert — just a slow disappearance from search results. The insidious quality of robots.txt mistakes is that they produce no explicit error; they simply cause pages to not be crawled. Sites that deploy robots.txt changes without testing have a meaningful risk of blocking their own content at scale.

Key Principles

Block only what genuinely should not be crawled; err on the side of allowing.
robots.txt prevents crawling, not indexing; a blocked URL can still appear in search results if linked from other pages.
Test every robots.txt change using Google Search Console's robots.txt Tester before deploying to production.
Never deploy a development-phase "Disallow: /" configuration to a production environment without a verified removal process in place.

Implementation

Specific, actionable steps to put this into practice.

Write robots.txt rules using specific path patterns rather than broad wildcards wherever possible.
Add a robots.txt Tester review to your deployment checklist for any site environment that is or might become publicly accessible.
Keep a version history of your robots.txt file; the ability to compare current and previous versions makes errors significantly easier to spot.

Verification

How to confirm this practice is correctly implemented.

Test the robots.txt file using Google Search Console's robots.txt Tester for every URL pattern you intend to block or allow.
Crawl the site with a crawler set to respect robots.txt and compare against a crawl that ignores it to identify which pages are being blocked.
Check Google Search Console's Coverage report for any 'Blocked by robots.txt' exclusions that affect pages you intend to be indexed.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using wildcard Disallow rules that accidentally block important content sections alongside the intended targets.
Deploying staging environment robots.txt configurations to production during site migrations.
Assuming that robots.txt blocking prevents a page from appearing in search results; it does not, if the page is linked from other sites.

At a Glance

Impact High

Effort Easy

Category Technical

Primary Source

Google Search Central

How to specify a canonical URL

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Technical High Effort: Easy

Consolidate Duplicate URLs with 301 Redirects

Use permanent 301 redirects to consolidate identical content under a single canonical URL when deprecating old pages or restructuring a site.

Why It Matters

When multiple URLs serve the same content, search engines split ranking signals across those variants. A 301 redirect is the strongest signal you can send to Google that a URL has permanently moved, ensuring that link equity and ranking history are passed to the new, preferred destination.

Key Principles

A 301 redirect is a definitive directive, whereas a canonical tag is merely a strong hint.
Redirects should point directly to the final destination, avoiding redirect chains.
Both users and search engines follow redirects, providing a seamless experience when content moves.

Implementation

Specific, actionable steps to put this into practice.

Identify duplicate pages or legacy URLs that are no longer needed but still receive traffic or have inbound links.
Implement server-level 301 redirects (e.g., via .htaccess or Nginx config) from the legacy URLs to the canonical URL.
Update internal links to point directly to the new canonical URL to reduce server load and crawl latency.

Verification

How to confirm this practice is correctly implemented.

Use a tool like curl or a redirect checker to verify the HTTP status code is exactly 301.
Crawl the site to identify and fix any internal links pointing to the redirected URLs.
Monitor Google Search Console's Page Indexing report to ensure the old URLs drop out of the index and the new ones take their place.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using 302 (temporary) redirects for permanent moves, which may prevent link equity from consolidating.
Creating redirect chains (A -> B -> C), which dilutes ranking signals and slows down page loading.
Redirecting deleted pages to the home page instead of a topically relevant alternative (resulting in soft 404s).

At a Glance

Impact High

Effort Easy

Category Technical

Primary Source

Google Search Central

Technical High Effort: Hard

Declare hreflang Annotations for Multilingual and Multi-Regional Sites

The hreflang attribute tells search engines which language and region each page targets, ensuring the correct localised version is served to the right audience.

Why It Matters

When you have multiple versions of a page for different languages or regions (e.g., an English site for the UK and an English site for the US), Google may see them as duplicate content. hreflang annotations explicitly tell Google about the relationship between these pages. This prevents keyword cannibalisation, ensures users get the correct currency and local information, and consolidates ranking signals across language variants.

Key Principles

Annotations must be bidirectional (reciprocal); if Page A links to Page B, Page B must link back to Page A.
Always include a self-referencing hreflang tag for the current page.
Use the x-default value to specify the fallback page for users whose language or region does not match any of the specified variants.

Implementation

Specific, actionable steps to put this into practice.

Add link rel=alternate hreflang elements to the head of your HTML, or implement them via HTTP headers or an XML sitemap.
Use correct ISO 639-1 language codes and optional ISO 3166-1 Alpha 2 region codes (e.g., en-gb for English in the UK).
Ensure all URLs specified in the hreflang tags are absolute, fully-qualified URLs, not relative paths.

Verification

How to confirm this practice is correctly implemented.

Use the International Targeting report in Google Search Console (or third-party crawling tools like Screaming Frog) to identify missing return tags or invalid language codes.
Inspect the page source to ensure the tags are correctly placed within the head section.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using incorrect country codes (e.g., en-uk instead of the correct en-gb for the United Kingdom).
Failing to implement reciprocal tags, which causes Google to ignore the annotation entirely.

At a Glance

Impact High

Effort Hard

Category Technical

Primary Source

Google Search Central

Localised Versions of Your Pages

Technical High Effort: Moderate

Ensure Mobile and Desktop Content Are Identical

Google crawls and indexes the mobile version of your site. Any content, links, or structured data missing from mobile is effectively invisible to search engines.

Why It Matters

Mobile-first indexing has been the default for all new sites since 2019 and has been applied to all sites. Googlebot's primary crawl uses a mobile user-agent. This means the content Google indexes is the content present on the mobile version of your site. Sites that show abbreviated content, fewer images, or stripped navigation on mobile are indexing an inferior version of their content. The failure is architectural: responsive design implementations that hide content on mobile for UX reasons are inadvertently hiding it from Google.

Key Principles

The mobile version must contain the same primary content, structured data, and internal links as the desktop version.
Content hidden on mobile via CSS display:none or JavaScript conditional rendering may not be crawled or indexed.
Page speed on mobile directly affects Core Web Vitals scores and the Page Experience ranking signal.
Google's mobile-first crawling applies to both responsive and separate mobile URL implementations.

Implementation

Specific, actionable steps to put this into practice.

Audit your site using Google's Mobile-Friendly Test and compare the rendered output against the desktop version for content parity.
Use CSS responsive design rather than separate mobile URLs where possible; maintaining two separate URL sets for content parity is operationally difficult.
Ensure structured data markup is present in the mobile HTML response, not loaded conditionally based on screen width or device type.

Verification

How to confirm this practice is correctly implemented.

Use Google Search Console's URL Inspection tool with the mobile user-agent setting to see exactly what Googlebot sees on mobile.
Compare word counts of key pages on mobile and desktop using a text extraction tool; significant differences indicate content parity issues.
Crawl the site with a mobile user-agent and compare the link graph against the desktop crawl to identify navigation elements missing on mobile.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using JavaScript to progressively reveal content on desktop whilst serving a simplified version to mobile, assuming users do not need it.
Including structured data only in desktop page templates without ensuring mobile templates carry the same markup.
Assuming that because the site 'looks fine on mobile' the content parity requirement is met.

At a Glance

Impact High

Effort Moderate

Category Technical

Primary Source

Google Search Central

Google Image SEO Best Practices

Related Troubleshooter Issues

If this practice is not in place, these are the issues you may encounter.

Technical Medium Effort: Moderate

Host Images on a Verified CDN Domain

When using a Content Delivery Network (CDN) for images, ensure the CDN domain is verified in Search Console to accurately track crawl errors and indexing status.

Why It Matters

CDNs improve page speed, but hosting assets on a third-party domain can create blind spots in SEO monitoring. Verifying the CDN domain allows you to submit cross-domain image sitemaps and receive critical alerts if Google encounters issues crawling your visual assets.

Key Principles

Image sitemaps permit cross-domain URLs, allowing you to explicitly declare CDN-hosted images.
Verifying the CDN domain provides access to crawl data specifically for those assets.
A fast, reliable CDN contributes to better Core Web Vitals and user experience.

Implementation

Specific, actionable steps to put this into practice.

Set up a custom subdomain for the CDN (e.g., images.example.com) and map it to the CDN provider.
Verify the custom CDN subdomain as a property in Google Search Console.
Generate and submit an XML image sitemap that includes the CDN URLs in the <image:loc> elements.

Verification

How to confirm this practice is correctly implemented.

Check the Index Coverage report for the verified CDN property in Search Console.
Test the CDN's robots.txt file using the robots.txt Tester to ensure Googlebot Image is allowed.
Verify that the image sitemap is successfully processed without cross-domain errors.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using a shared, generic CDN URL without verifying ownership, losing visibility into crawl errors.
Failing to update the image sitemap when migrating assets to a new CDN.
Blocking Googlebot from crawling the CDN domain via a misconfigured robots.txt on the CDN server.

At a Glance

Impact Medium

Effort Moderate

Category Technical

Primary Source

Google Search Central

Technical Medium Effort: Easy

Implement Breadcrumb Schema Markup for Navigation

BreadcrumbList schema explicitly defines your site hierarchy for search engines, enabling clean breadcrumb trails in search results instead of raw URLs.

Why It Matters

Google Search uses breadcrumb markup to categorise the information from the page in search results. Instead of showing a raw URL string, Google can display a clean, readable path (e.g., Home > Category > Product). This helps users understand where the page sits within your site's hierarchy before they click, and provides search engines with clear signals about your site architecture and internal linking structure.

Key Principles

The breadcrumb trail must represent the actual navigational path to the current page.
Each item in the breadcrumb chain must include a name and a URL, except typically the final item (the current page), which does not need a URL.
The structure should logically progress from the broadest category (usually the homepage) down to the specific page.

Implementation

Specific, actionable steps to put this into practice.

Add JSON-LD BreadcrumbList schema markup to the head of your pages.
Ensure the position property is correctly incremented for each ListItem in the chain (1 for Home, 2 for Category, etc.).
Ensure the visual breadcrumbs displayed on the page match the structured data provided in the markup.

Verification

How to confirm this practice is correctly implemented.

Use the Google Rich Results Test tool to validate that the breadcrumb schema is implemented correctly and is eligible for rich results.
Monitor the Enhancements > Breadcrumbs report in Google Search Console for any parsing errors or warnings.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Including the current page in the schema with a link to itself, creating a circular reference.
Implementing breadcrumb schema that contradicts the actual site architecture or visual navigation.

At a Glance

Impact Medium

Effort Easy

Category Technical

Primary Source

Google Search Central

BreadcrumbList Schema Markup

Technical High Effort: Hard

Implement Proper hreflang for International Sites

hreflang tells Google which language and region variant of a page to serve to which users. Incorrect implementation causes the wrong language version to appear in the wrong country's search results — one of the most frustrating and difficult-to-diagnose SEO problems.

Why It Matters

Google's documentation is explicit: "Use hreflang to tell Google about the variations of your content, so that we can understand that these pages are localized variations of the same content." Without correct hreflang, Google must guess which version to show to which user — and it frequently guesses wrong. The most common consequence of missing or incorrect hreflang is that the English version of a page ranks in markets where the local language version should appear, resulting in poor user experience and lower conversion rates.

Key Principles

All language variants must reference each other in a complete set
Use ISO 639-1 language codes and ISO 3166-1 Alpha 2 country codes
Use `x-default` for the fallback page shown when no specific variant matches

Implementation

Specific, actionable steps to put this into practice.

Choose an implementation method: HTML link elements, HTTP headers, or XML sitemap
For each page, add hreflang annotations for all variants including a self-reference
Validate the implementation using Google Search Console's International Targeting report
Test that the correct variant appears in search results for each target market

Verification

How to confirm this practice is correctly implemented.

Manual search in each target market using a VPN or Google's country-specific search domains
Screaming Frog's hreflang audit to identify missing self-references and broken annotations

Common Mistakes

Pitfalls and anti-patterns to avoid.

Using incorrect language or country codes
Pointing hreflang annotations at redirected or non-canonical URLs
Implementing hreflang on only some pages of a multi-language site

At a Glance

Impact High

Effort Hard

Category Technical

Primary Source

GOOGLE SEARCH CENTRAL

Localized Versions of Your Pages

Technical Medium Effort: Easy

Maintain an Accurate XML Sitemap

An XML sitemap is your explicit declaration to Google of what pages exist and when they were last updated. It should be accurate, maintained, and contain only indexable canonical URLs.

Why It Matters

A sitemap with errors trains Google to distrust your crawl signals. A sitemap full of redirected, 404, or noindexed URLs wastes the signal it is meant to optimise. The most common failure is not generating a sitemap but maintaining it: sitemaps generated at launch and never updated accumulate dead URLs and miss new content. For large sites, an accurate sitemap is essential for ensuring Googlebot allocates crawl budget to live content rather than wasting it discovering URLs you already know about.

Key Principles

Sitemaps should contain only canonical, indexable URLs that return a 200 HTTP status.
The lastmod attribute should accurately reflect when content was last meaningfully updated, not server-generated timestamps.
Sitemap index files should be used for sites with more than 50,000 URLs.
Sitemaps should be submitted to Google Search Console and updated whenever significant content changes occur.

Implementation

Specific, actionable steps to put this into practice.

Configure your CMS to generate sitemaps dynamically so new pages are added and removed pages are deleted automatically.
Validate your sitemap using Google Search Console's Sitemaps report and an XML validator after every significant content structure change.
Set lastmod dates from actual content update timestamps rather than from server generation time, which inflates recency signals without benefiting ranking.

Verification

How to confirm this practice is correctly implemented.

In Google Search Console, compare the submitted URL count against the indexed URL count. A significant discrepancy indicates URLs in the sitemap that Google cannot or will not index.
Crawl your sitemap using Screaming Frog's sitemap crawl feature to identify any 4xx, 5xx, redirected, or noindexed URLs that should be removed.
Check that your sitemap is referenced in robots.txt for maximum discoverability by crawlers.

Common Mistakes

Pitfalls and anti-patterns to avoid.

Including redirected or deleted URLs in sitemaps after content restructuring, creating conflicting indexation signals.
Generating lastmod timestamps from the current server time rather than actual content update time.
Submitting a sitemap once at launch and never updating it as content changes over the following months and years.

At a Glance

Impact Medium

Effort Easy

Category Technical

Primary Source

Google Search Central