Skip to content

Ch 13 — The display layer

Part V — Site design · The Technical SEO Reference

Playbook coupling: seo-checklist.md treats display-layer items in Phase 2 (title, line 122; meta description, line 126) and Phase 1 (site name + favicon, line 112), and its mental model #1 already states the doctrine: titles/snippets are "the display layer — they change clicks, not rankings." This chapter covers the generation side the playbook has no room for: how Google constructs title links, when it uses vs replaces your meta description, how it detects dates, how site names are chosen, and how sitelinks form — the mechanics behind "Google rewrote my title" and "Google shows the wrong date."

Everything in this chapter shares one property: Google generates it; you influence it. The title link, snippet, byline date, site name, and sitelinks are all assembled at query time from signals you supply plus signals you don't control. The practitioner's job is to make your preferred version the path of least resistance — and to know, when Google overrides you, which signal it reached for instead. All quotes below fetched live 2026-08-04.

From the title links doc (last updated 2025-12-10):

🟢 The complete documented source list — what Google draws on to generate a title link: 1. "Content in <title> elements" 2. "Main visual title shown on the page" 3. "Heading elements, such as <h1> elements" 4. "Content in og:title meta tags" — ⚠️ added to the documented list Aug 23, 2024 (changelog: "Added og:title to the list of title link sources"; trade coverage Aug 26); OpenGraph is a 📘 standards-layer input that Google now officially reads for titles 5. "Other content that's large and prominent through the use of style treatments" 6. "Other text contained in the page" 7. "Anchor text on the page" 8. "Text within links that point to the page" — external anchors can title your page 9. WebSite structured data

🟢 Why rewrites happen: "Google Search tries to determine if the <title> element isn't accurately showing what a page is about… modify the title link to better help users," and "If we've detected an issue on the page, we may try to generate an improved title link from anchors, on-page text, or other sources." A rewrite is a diagnosis: Google judged your title element inaccurate, stuffed, boilerplate, or missing. The doc's named anti-patterns map 1:1 to rewrite triggers: - "Avoid keyword stuffing… there's no reason to have the same words or phrases appear multiple times." - "Avoid repeated or boilerplate text in <title> elements… distinct text that describes the content" — sitewide "Cheap Flights | Brand | Best Prices | Book Now" templates invite rewriting. - Half-empty or missing titles → Google builds one from anchors and headings.

🟢 No character limit: "While there's no limit on how long a <title> element can be, the title link is truncated in Google Search results as needed, typically to fit the device width." The playbook's ⚪ label on "50–60 chars" (line 122) stands — it's a display heuristic about truncation, not a Google rule.

🟢 Site-name interaction: "Google may omit the site name from the title link, if it's repetitive with the site name that's already shown" — since site names render as their own SERP element (§13.4), | BrandName suffixes are increasingly redundant on mobile.

⚠️ Diagnostic method for rewrites: compare the served title link (search site: for the exact URL) against your <title>; if rewritten, check which source Google used — it is usually recognizable as your H1, a prominent styled heading, or repeated inbound anchor text. Fixing the source Google chose (or fixing the title defect that triggered the swap) is the lever; there is no opt-out.

13.2 Snippets — generation and the meta-description conditions

From the snippet doc (last updated 2026-04-20):

  • 🟢 The hierarchy: "Snippets are primarily created from the page content itself. However, Google sometimes uses the meta description HTML element if it might give users a more accurate description of the page than content taken directly from the page." Your meta description is a candidate, evaluated per query — page text that matches the query better wins.
  • 🟢 The exact condition, restated: Google uses the tag "if we think it gives users a more accurate description than would be possible purely from the on-page content." Consequence: query-dependent snippets are normal; a page ranks for many queries and can show a different snippet for each.
  • 🟢 The pitch framing (the playbook's Phase 2 line 126 source): meta descriptions "are like a pitch that convince the user that the page is exactly what they're looking for."
  • 🟢 No length limit: "There's no limit on how long a meta description can be, but the snippet is truncated in Google Search results as needed, typically to fit the device width."
  • 🟢 Uniqueness: "Identical or similar descriptions on every page of a site aren't helpful when individual pages appear in search results" — template-generated identical descriptions are effectively no descriptions.
  • 🟢 The control levers (inventory and semantics → Ch 7 §7.3, their canonical home): nosnippet kills the snippet; data-nosnippet excises sections; max-snippet:[n] caps length. ⚠️ These also gate AI-surface eligibility — snippet-eligible is the AI Overviews entry condition (→ Ch 5, playbook Phase 6) — so "control the snippet" decisions now carry AI-visibility consequences.

⚠️ Why your description was replaced — the checklist: (1) it didn't answer the query the searcher typed; (2) it's boilerplate/duplicated sitewide; (3) it's missing; (4) page text simply matched better. Writing per-page descriptions that front-load the page's actual answer minimizes — never eliminates — replacement.

13.3 Dates — how Google decides when your page was published

From the publication dates doc (last updated 2025-12-10):

  • 🟢 The model: "A byline date is the date that Google estimates that the web page was updated or published," and — the load-bearing sentence — "Google doesn't depend on a single date factor because all factors can be prone to issues." It triangulates: the visible date, structured data, and other signals. You cannot dictate the date; you can only make all your signals agree.
  • 🟢 Best practices, verbatim: "Add a user-visible date to the page and feature it prominently"; "Label your dates appropriately with text like 'Publish' or 'Last updated'"; supply datePublished and/or dateModified on a CreativeWork subtype (Article, BlogPosting, VideoObject); and ⚠️ the consistency rule: "Make your dates and times consistent. Ensure that the date (and optional time and timezone) match between the equivalent user-visible and structured values" — mismatched visible-vs-markup dates are the #1 cause of "Google shows the wrong date."
  • 🟢 Format mechanics: ISO 8601 in structured data ("2021-07-20T08:00:00+08:00"); "The date is required; the time is not"; "provide the correct timezone, taking into account daylight saving time."
  • 🟢 ⚠️ The anti-freshening rules: "Don't specify future dates, or the date of the action described on the page" — dates "must describe the publication or update date of the page, not the stories or events described therein." This is the technical face of the playbook's fake-freshness ⛔ (quality-guidance list, line 248): date-bumping without substantive change is both a people-first self-assessment failure and — because Google triangulates — frequently doesn't even work: the visible date changes, other signals don't, and Google keeps showing the old estimate.
  • ⚪ For news/Discover properties, date accuracy is commercially load-bearing (freshness display drives CTR) — which is why date manipulation is endemic there and why Google's estimator distrusts single signals.

13.4 Site names

From the site names doc (last updated 2025-12-10):

  • 🟢 Generation: "completely automated and takes into account content from a site's home page and references to it that appear on the web." Preference signal ranking: "add WebSite structured data to your home page. Our site name system will also consider content in og:site_name, <title>, heading elements, and other text on a home page. However, WebSite structured data is most important, if you want to specify a preference."
  • 🟢 The root-URI rule: "The WebSite structured data must be on the home page of the site. By home page, we mean the domain or subdomain level root URI." Subdomain home pages are supported (news.example.com); ⚠️ subdirectory-level "home pages" are not (example.com/news) — a subfolder brand cannot have its own site name.
  • 🟢 Crawlability: "If we don't have access to the content on your home page because it is blocked, we may not be able to generate a site name" (→ Ch 3).
  • 🟢 name vs alternateName: name is the site name; alternateName carries an acronym or shorter name for the site, if applicable.
  • 🟢 Troubleshooting, per the doc: verify structured-data accuracy → ensure redirects work → use consistent naming across site versions (og:site_name, title, WebSite markup all agreeing — the playbook's line 112 discipline, and the exact mechanism behind the bk8mypro entity-consistency work) → allow recrawl time.

From the sitelinks doc (last updated 2025-12-10):

  • 🟢 "Sitelinks are links from the same domain that are clustered together under a text result… At the moment, sitelinks are automated." Display is conditional: "We only show sitelinks for results when we think they'll be useful to the user. If the structure of your site doesn't allow our algorithms to find good sitelinks, or we don't think that the sitelinks for your site are relevant for the user's query, we won't show them."
  • 🟢 The influence levers are ordinary architecture (→ Ch 10): "informative, relevant, and compact" titles and headings; "a logical site structure that is easy for users to navigate… link to your important pages from other relevant pages"; "internal links' anchor text is concise and relevant"; "avoid repetitions in your content."
  • 🟢 ⚠️ No direct control exists. There is no markup to request sitelinks and no demotion tool (retired Oct 13, 2016 — 🟡 announced on Google+, per SEL/SER trade coverage; the primary post died with Google+): "If you need to remove a sitelink, consider removing the page from your site or using noindex" — a blunt instrument, usually worse than living with the sitelink.
  • ⚠️ The sitelinks search box is a separate, retired feature (Nov 2024, → Ch 12 §12.5); regular sitelinks are alive and unaffected.

13.6 The display layer as a diagnostic surface

The playbook's master diagnostic (mental model #4: impressions steady + clicks down = display-layer problem) lands here. When CTR drops without ranking movement, audit in this order:

  1. Title link: is Google serving your title or a rewrite? Did a recent template change introduce boilerplate that triggered rewriting? (§13.1)
  2. Snippet: did the served snippet change — meta description newly replaced, or a max-snippet/data-nosnippet deployment bite? (§13.2)
  3. Date: did the byline date regress (a triangulation change after a redesign moved/unlabeled the visible date)? Stale-looking results bleed CTR on freshness-sensitive queries. (§13.3)
  4. Site name / favicon: did the SERP identity change — wrong site name selected, favicon lost? (§13.4; favicon → Ch 14)
  5. Competing SERP furniture: rivals gained rich results (→ Ch 12) or AI Overviews began absorbing the query's clicks (→ playbook Phase 6/7) — your listing unchanged, its environment worse.

Symptoms & diagnosis

Symptom Likely cause Where
Google shows a different title than your <title> Rewrite triggered: stuffing, boilerplate, inaccuracy — check which source was substituted §13.1
Meta descriptions "ignored" sitewide Duplicated/template descriptions, or page text matches queries better §13.2
Different snippets for the same page Normal — per-query generation §13.2
SERP shows wrong/old date Visible-vs-structured date mismatch; unlabeled date; triangulation distrust after date-bumping §13.3
Wrong site name on results WebSite markup missing/conflicting with og:site_name/title; not on root URI; blocked homepage §13.4
Subfolder property shows parent's site name Subdirectory site names unsupported — by design §13.4
Unwanted sitelink appearing No demotion tool — restructure, or noindex/remove the target page §13.5
CTR down, rankings flat Work §13.6's audit order §13.6

Sources

All fetched live 2026-08-04 by the drafter: - Title links (2025-12-10) - Snippets and meta descriptions (2026-04-20) - Publication/byline dates (2025-12-10) - Site names (2025-12-10) - Sitelinks (2025-12-10) - V2 audit 2026-08-04: both prior V2 items resolved — og:title's addition to the title-link source list is dated Aug 23, 2024 in Google's changelog (the earlier "May 2024" attribution was wrong; corrected in §13.1); sitelinks-demotion-tool retirement pinned to Oct 13, 2016 (🟡 Google+ announcement, per trade press). All five appearance docs re-verified live this date.