Repository navigation
Conversation
|
No actionable comments were generated in the recent review.
 |
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title clearly and concisely identifies the main change: adding data-nosnippet to the related-posts section to prevent snippet contamination. |
| Description check | |
The description directly explains the snippet-selection problem, the data-nosnippet solution, affected file, testing, and expected behavior. |
| Docstring Coverage | |
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
Problem
Google can select text from the "Read more" related-posts section at the
bottom of a post page as the search-result snippet for that page, instead of
the post's own content — even though the related posts are unrelated to the
page's actual topic.
For example, a search for "WordA WordB" returned a result linking to a post
whose title contains "WordA", but with a snippet containing "WordB" — text
that doesn't appear anywhere in that post, but does appear in the title/
excerpt of an unrelated post shown in its "Read more" section.
Solution
Add the data-nosnippet attribute to the
<section>already wrapping the related-posts block inpost.hbs.This tells Google to never use this section's text for a search snippet
(applies to both classic web search and AI Overviews/AI Mode, per Google's
docs), while leaving the section, its links, and its visual layout completely
unchanged for real visitors.
data-nosnippetonly affects snippet text selection — it does not changecrawling, link-following, or indexing behavior in any way. The related-posts
links remain fully crawlable and followable, the section's content stays
indexed and eligible for ranking.
data-nosnippetis documented by Google as supported onspan,div, andsectionelements specifically — the existing wrapper is already a<section>, so no tag change is needed, just the one attribute:Alternatives considered
We considered semantic-only alternatives (e.g. wrapping the section in
<aside>instead of<section>), but tag choice alone has no documentedeffect on Google's snippet selection —
data-nosnippetis the actual,documented mechanism for this, and Google only guarantees it on
span,div, andsection.Files
post.hbs— 1 line changed (addeddata-nosnippetattribute, no otherchanges)
Testing
pnpm install --frozen-lockfile+pnpm test:ci(gulp zipthengscan --fatal --verbose .) — ✓ no fatal compatibility issues with Ghost 6.x.data-nosnippethas no CSS or rendering effect.Browser support
data-nosnippetis inert everywhere except crawlers that recognize it —currently Google (web search and AI Overviews/AI Mode) and, as of October
2025, Bing.
It's a plain HTML
data-*attribute with zero visual or functional effect inany browser or any crawler that doesn't recognize it.
Co-developed with GitHub Copilot.