You update a page title and meta description, deploy the site, and Google still shows the old wording. Rewriting the description again is rarely the best first move. Check the deployed HTML and Google’s last crawl first.
The short answer is that Google does not promise to display <title> or <meta name="description"> verbatim. They are important signals, but Google can generate title links and snippets from the query, visible page content, and other page-level signals.
This creates three separate questions: did the new HTML reach production, has Google recrawled it, and does Google consider another passage more useful for this query?
Verify the deployed page first
Local source changes do not prove that the public page changed.
[ ] The live <title> contains the new value
[ ] The live meta description contains the new value
[ ] The old wording is gone from the opening content
[ ] The canonical points to the intended URLInspect the response directly:
curl -L https://example.com/ | grep -E "title|description"For a static site, inspect the build output as well:
dist/index.html
dist/en/index.html
dist/sitemap-index.xmlIf the old copy remains in production, the search engine is not stale—it is seeing stale output.
A meta description is a candidate, not a command
Google’s snippet documentation says snippets are created primarily from page content. It may use the meta description when that text describes the page better, and the selected snippet can vary by search query.
That means changing the meta description does not guarantee an identical search-result update. The same page can also show different passages for different queries.
Treat the description as a strong page summary, not a reserved search-result field. The opening paragraph, headings, visible text, and query relevance still matter.
Google can rewrite the title link too
Google uses multiple sources for title links. The <title> element is central, but the visible page title, prominent text, language, and link text can also contribute.
| Signal | What to check |
|---|---|
<title> |
A clear, page-specific title |
<h1> |
The main visible heading describes the same topic |
| Internal anchors | Other pages name this URL consistently |
| Repeated boilerplate | Titles remain distinguishable across pages |
| Language | The title and main content use the page’s language |
The search-oriented title can be more specific than the on-page H1, but both should still describe the same page.
Common reasons the old wording remains
| Cause | Symptom | Check |
|---|---|---|
| Google has not recrawled | Live HTML changed; result did not | Search Console URL Inspection |
| Old copy remains in page content | Part of the old snippet still appears | Search source and built HTML |
| Description is generic | Google chooses a visible passage instead | Write a page-specific summary |
| Title and H1 disagree | Result title differs from expectation | Compare title, H1, and link anchors |
| Canonical points elsewhere | Another URL is treated as representative | Inspect rel="canonical" |
| Indexing directives conflict | Index state is unexpected | Check noindex and robots rules |
| Sitemap metadata is stale | Change signals are weak | Inspect sitemap lastmod |
Static sites often leave old copy in a home card, list description, footer, or generated output. Search the source and the build:
rg "old wording|replacement wording" src public distDo not stop at src. The crawler receives the generated HTML in dist or its deployed equivalent.
Canonical signals matter just as much. If you update /en/posts/a/ while its canonical points to an old route, Google may continue treating the other URL as the representative page.
A recrawl request is not an instant update button
For one URL, use Search Console URL Inspection. For broader changes, keep the sitemap accurate. Google’s recrawl documentation says crawling may take days to weeks and that a request does not guarantee immediate inclusion or display changes.
Use this order:
1. Verify the deployed HTML
2. Check the URL and lastmod in the sitemap
3. Inspect the URL in Search Console
4. Request indexing once
5. Recheck over days, not minutes
6. Review actual queries and CTR in Search ConsoleRepeated submissions do not force a faster snippet change. They only repeat the request to revisit the page.
Write descriptions that accurately summarize the page
Google does not publish a fixed meta-description length requirement, although displayed text can be truncated. Precision matters more than hitting a target character count.
[ ] Each page has a distinct description
[ ] It adds information instead of repeating the title
[ ] It tells the reader what decision or answer they will get
[ ] It avoids unsupported clickbait
[ ] It agrees with the opening content“Everything you need to know about SEO” is broad and untrustworthy. “Why a deployed title and meta-description change can remain absent from Google results, and how to check recrawling” makes a testable promise.
Static-site publishing checklist
| Stage | Verify |
|---|---|
| Writing | Title, display title, and description promise the same topic |
| Build | Title, description, and canonical appear in generated HTML |
| Search | Old copy is absent from source, public assets, and output |
| Deploy | Sitemap, feed, and lastmod are current |
| Index | noindex and robots behavior match your intent |
| Operate | Search Console shows the real queries and resulting snippets |
If Google still shows the old text, stop changing the copy blindly. Make production HTML internally consistent, verify canonical and index signals, then give recrawling time to happen.