PublishedVerifiedEvery 6 weeksSources6 namedAuthored bySquareRank Team
Gemini · § 1.4.2 · How-to
The Squarespace Gemini Freshness Signal, Honestly
Gemini's grounding draws from Google Search results1, which means Google's freshness systems — Query Deserves Freshness and the December 2025 core update2 — flow through to which Squarespace pages Gemini cites. The Squarespace gotcha is small but real: the auto-emitted Article schema does not reliably update dateModified when only body content changes, and sitemap lastmod sometimes misses content-only edits too. The fix is one Code Injection block and a quarterly refresh calendar.
This leaf ships the supplemental JSON-LD block, the visible date strip pattern, and the editorial discipline that separates substantive updates from cosmetic ones. Google's December 2025 core update tightened the distinction between the two, which makes honest dateModified handling more useful than the date-rotation tricks 2023-era SEO blogs recommended.
§01The short answer
TL;DR — fresh content earns Gemini citations more reliably
Three layers compound: a JSON-LD Article block with an honest dateModified value, a visible date strip on the page that matches it, and a quarterly review cadence that bumps both when the underlying claims change. The work itself is small — about thirty minutes per page on the initial pass and ten minutes per page on each refresh — but the discipline is what separates real freshness from theatre. Google's December 2025 core update specifically targeted cosmetic date-rotation, so the only freshness move that pays in 2026 is actually updating the content.
The classical-SEO foundation matters here. Gemini citation eligibility starts with classical Search ranking, and classical Search ranking on topical or news-leaning queries is heavily influenced by Google's freshness systems. The same dateModified discipline that helps ranking helps Gemini citations, and the same date-rotation theatre that no longer helps ranking also does nothing for Gemini. One investment, two payoffs.
§02The mechanism
What freshness means for Gemini grounding
Gemini's grounding tool fires Google Search queries when it needs live web information. The returned candidate set reflects Google's main Search ranking, which on topical and news-leaning queries is weighted by Query Deserves Freshness. Newer pages with accurate dateModified signals out-rank stale ones, and Gemini reads the resulting top-ranked pages when synthesising its answer. So the path from 'fresh content' to 'Gemini citation' runs through classical Search ranking — there is no separate Gemini-freshness signal you can tune in isolation.
Search Engine Land's QDF guide2 documents the underlying systems. QDF activates when news coverage spikes, social signals jump, and search volume rises on a topic in parallel. The December 2025 core update added another layer: the system now distinguishes substantive content updates (new data, expanded sections, revised recommendations) from cosmetic ones (date rotated, a few words swapped). The latter no longer moves ranking.
For Squarespace owners, the practical implication is that you cannot fake the freshness signal in 2026. Bumping dateModified without changing the underlying claims used to work for a brief window between 2019 and 2023. Then Google added the substantive-vs-cosmetic detector. Treat the date as a truthful record of when the content actually changed, and the freshness layer pays. Treat it as a tweakable SEO knob and it costs you more than it earns.
The freshness math for Gemini citation
+33%
Gemini referral traffic growth Nov 2025 → early Jan 2026, concentrated on decision-support queries (BrightEdge).
What Squarespace ships by default — and where it falls short
Squarespace auto-emits some Article-shape metadata on blog posts: title, author, publish date. The dateModified field is the awkward part. On many 7.1 blog posts, dateModified is either missing entirely from the auto-emitted JSON-LD or equal to datePublished, which gives Google no useful signal for whether the content has been updated since first publish. Sitemap lastmod values can also lag content-only edits. The result is a freshness signal that under-represents work the site has actually done.
Squarespace's content metadata documentation5 covers the publish-date field but does not explicitly document the dateModified behaviour. Multiple community threads have reported inconsistent updates: a content edit on Tuesday does not always bump dateModified, and the next sitemap regeneration may or may not pick up the change. The behaviour appears more reliable on collection items (blog posts) than on regular section-based pages, but neither is consistent enough to leave to the platform.
The fix is supplemental Code Injection. Inject a small JSON-LD block in Page Settings → Advanced → Code Injection → Header that re-declares the Article schema with an explicit dateModified value. Google's Article schema documentation3 handles duplicate Article schema gracefully — the explicit values in your injection take precedence over the auto-emitted ones. Schema.org's dateModified specification4 defines the field as the date on which the work was most recently modified, in ISO 8601 format.
§04The patch
The Code Injection patch for dateModified
The patch is a minimal Article JSON-LD block scoped to the page it lives on, with an explicit dateModified field in ISO 8601 format. Inject it into Page Settings → Advanced → Code Injection → Header on each editorial page. The author and publisher fields should point to the founder Person URL and the Organization URL respectively, matching the entity wiring the AI Overviews E-E-A-T leaf covers. Update the dateModified value each time you make a substantive content change.
Two implementation notes. First, the patch requires Code Injection access, which is locked to Business plan and above. On Personal plan, the workaround is to live with the Squarespace auto-emitted schema and put more weight on the visible date strip pattern in the next section. Second, the date format must be ISO 8601 (YYYY-MM-DD or full RFC 3339 with timezone). Google rejects ambiguous formats like "May 18, 2026" silently in the structured-data parser.
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"Your Page Title Here","datePublished":"2026-05-18","dateModified":"2026-05-18","author": {"@type":"Person","name":"Founder Name","url":"https://yoursite.com/founder/"},"publisher": {"@type":"Organization","name":"Your Brand","url":"https://yoursite.com/"}}</script>
Validate via Google's Rich Results Test (search.google.com/test/rich-results) after pasting. Expect zero errors. The Article schema is informational rather than rich-result triggering for general editorial pages, so the absence of a rich-result preview in the test is not a failure — the schema parses successfully and feeds Google's understanding of the page, which is the actual goal.
§05The visible strip
The visible date strip on the page
Schema-level freshness is necessary but not sufficient. Google's documentation explicitly says the date values shown to users should match the structured-data values. The visible date strip — the small Published + Verified + Sources + Authored row at the top of every editorial page on this site — is the visible side of the same discipline. When users (and the freshness systems) see a recent date in the page header, they read the rest of the content with corresponding expectations.
The pattern is editorial, not technical. Pick a four-cell strip layout (Published date, Verified date or cadence, Source count, Author byline). Ship the same shape on every editorial page. Update the visible value the same time you update the JSON-LD value — never one without the other. The mismatched-date case is worse than the missing-date case because it signals carelessness to both users and the engine.
§06The cadence
The quarterly refresh cadence
Set a calendar reminder ninety days after each page's modified date. The reminder triggers a substantive review: are the claims still accurate, do the sources still resolve, have any vendor names or statistics moved? The discipline is to either update something material and bump the date, or leave both alone. The third option — bumping the date without updating anything — used to work briefly in the early 2020s and now actively hurts.
A simple spreadsheet works: one row per editorial page, columns for URL, modified date, next-review date, and a notes field for what changed on the last review. Sort by next-review date weekly and the queue manages itself. Pages with topical or news-leaning content may warrant a six-week cadence (the 'Verified every 6 weeks' label this site uses); evergreen pages can stretch to six months.
§07Avoid these
Common mistakes to avoid
Three mistakes show up on most Squarespace audits. First, bumping dateModified on every page without actually changing anything — the cosmetic-date pattern Google's December 2025 core update specifically targeted. Second, mismatched dates between the visible strip and the JSON-LD. Third, treating the publish date as immutable when the page has been substantially rewritten — sometimes the honest move is to update both dates because the page is materially new content.
The discipline that beats all three is the same one this leaf has been building toward: be honest about what changed. If the page is rewritten end to end, datePublished can change too because it is functionally a new page. If only the third section is updated, bump dateModified and leave datePublished alone. If nothing changed, do not touch either date. The freshness layer pays when the dates carry information; it costs when they are noise.
With the freshness layer in place, the next layer in the cluster is the multimodal asset hygiene that lives in the multimodal leaf. Gemini is natively multimodal, and image-level signals (alt text, file names, ImageObject schema) compound with the freshness work to make pages more readily citable across the model's grounding pipeline.
