Hreflang XML sitemap generator
Build a sitemap with xhtml:link hreflang annotations for localized pages, with every alternate listed on every URL as Google's documentation requires.
Paste many pages at once and see which titles and descriptions will truncate in Google search results, measured in pixels.
Runs entirely in your browser. Nothing you enter is uploaded, logged or stored.
| URL | Title | Title width | Description | Description width |
|---|
Uses the same canvas pixel-width measurement as thesingle-page SERP preview tool- check one page there, check many pages here.
Most title and description problems are not written by a person typing into one field, they are generated by a template. A product page layout that always appends ”| Brand Name - Free Shipping” to a title works fine for short product names and silently truncates for long ones, and nobody notices until dozens of listings in search results end mid-word.
A single-page preview tool answers one question well: does this one title fit. It cannot answer the question that actually matters at scale, which is whether the pattern your CMS or your templating logic produces holds up across every page that uses it. Paste an export of fifty product titles built from the same template and a systemic problem, such as a category name that pushes every title past the pixel budget, shows up as a cluster of highlighted rows rather than one edited field.
For a one-off check while editing a single page, the SERP snippet preview tool is faster: it shows the rendered snippet itself, not just a pass or fail width, which helps when you are still writing the copy rather than auditing what already shipped. Use that tool while drafting a page, and use this one after a crawl or export to confirm the whole site follows the pattern you intended.
A row marked truncated on mobile but not on desktop is not a bug in the tool, it reflects a real difference in how much width each layout allows. Fix the copy for the narrower of the two limits if the page needs to hold up everywhere, or accept the mobile truncation if the front-loaded part of the title still carries the meaning on its own.
A single-page preview only ever shows you one outcome. Most truncation problems are not one bad title, they are a template that produces the same too-long pattern on every product page or every blog post. Checking a batch is the only way to see that pattern rather than one symptom of it.
The exact same way as the single-page SERP preview tool, by drawing each string with the browser's canvas text API at the font sizes Google uses in results, then reading back the rendered width. That is closer to real truncation than any character-count rule.
Build a sitemap with xhtml:link hreflang annotations for localized pages, with every alternate listed on every URL as Google's documentation requires.
Paste status codes and see how Google's crawlers document handling each one, plus a redirect hop count against Google's 10-hop default.
Audit the links in pasted HTML against Google's rel qualifiers: sponsored for paid links, ugc for user content and nofollow when neither applies.
Validate robots meta tags and X-Robots-Tag headers against the rules Google documents, and see the combined result for Googlebot.