Screpy's Google SERP Simulator helps you compare a page title, meta description and URL in an illustrative search listing. Write a draft or load metadata from a public page, prepare the preview, then edit the wording and compare desktop and mobile layouts. The useful outcome is a clearer, accurate set of metadata to review before publication.
This is not a live Google result. The simulator does not search a query, measure rankings or predict clicks. Google can choose different title and snippet text, so use the preview to make editing decisions rather than treat it as a screenshot of a future search result.
Choose manual text or load a public page
Use manual mode for unpublished content or wording you want to change before touching the website. Supply a complete page URL and a title. The URL gives the illustration an address; manual mode does not fetch that page. The description and site name are optional, though an absent description is flagged for review.
Use Load from URL to start from the HTML returned by an existing public page. Redirects can change the final address shown in the preview. This mode reads the page's source metadata, not a saved Google listing or JavaScript-generated changes.
| Field | Purpose and editor limit |
|---|---|
| Page URL | Required in both modes; up to 2,048 characters. |
| Page title | Required for manual input; up to 200 characters. |
| Description | Optional summary; up to 1,000 characters. |
| Site name | Optional illustrative label; up to 80 characters. |
| Search query | Optional phrase highlighting; up to 100 characters. |
Prepare the preview, then edit the wording. Title, description and site-name edits update the illustration locally without a new analysis request on each keystroke. The device and query controls help you compare the same draft. These input limits belong to this editor; they are not recommended metadata lengths.
Write a snippet that describes the actual page
Imagine a fictional guide explaining how to plan a first welcome email, choose one next step and check it before sending. The following drafts are editorial examples, not generated or tested Google results.
| Draft | What the reader can infer |
|---|---|
| Title: Email Marketing Tips and Tools | Too broad to identify this particular guide. |
| Title: How to Plan Your First Welcome Email | Names the page's specific task. |
| Description: Double your sales with the perfect welcome email. | Promises a result the example page does not establish. |
| Description: Plan a first welcome email, choose one next step and check the message before sending. | Describes the actual scope without inventing an outcome. |
Read the title and description together. The title should identify the page; the description can explain what a visitor will find there instead of repeating the same words. Remove generic claims and put the distinguishing subject early enough to remain understandable if later text is clipped.
Do not add a discount, statistic, deadline or number of steps merely to make the listing look more attractive. The page must support those details. A shorter but inaccurate promise is not an improvement. Keep metadata specific to this page and consistent with the language and purpose of its visible content.
Compare desktop and mobile without chasing a fixed limit
Switch between desktop and mobile after preparing the preview. This tool uses different local widths and line allowances. Inspect whether the most important meaning survives in both layouts, rather than trimming until a particular character number looks desirable.
| Indicator | What it tells you | What it does not prove |
|---|---|---|
| Character count | The amount of supplied text, counted as Unicode code points. | A fixed pixel width or an optimal Google length. |
| Text fits | The current draft fits this preview's font, width and line settings. | Google will display the complete same text. |
| Clipping warning | Part of the title or description is hidden in the local layout. | The page has a ranking penalty or invalid metadata. |
Letters, writing systems and combined symbols occupy different amounts of space. Some visible symbols contain multiple code points. A count helps compare drafts but is not a pixel measurement.
Google's title-link guidance and snippet guidance specify no fixed title or meta-description character limit; displayed text is shortened as needed, typically for device width. Preserve essential meaning first, then remove redundancy. Do not delete a necessary condition solely to fit an arbitrary 60- or 160-character target.
Use query highlighting and site names as editing aids
Enter a phrase in the optional query field to highlight matching text in the description. For the example guide, try welcome email and judge whether the surrounding sentence still reads naturally. This is a literal phrase-matching aid, not a search, synonym analysis or relevance score. Highlighting does not verify that anyone searches the phrase.
The site-name field adds a label to the illustration. It does not append a brand to your title automatically, publish site-name markup or determine what Google will select. Google distinguishes the site name from the page's title link; they are separate elements with different purposes.
The simulator does not create star ratings, ads, AI Overviews or rich-result eligibility. Keep those separate from the question this preview can answer: whether the supplied title and description form a clear, plausible listing. For actual returned organic results, use the Keyword Rank Checker rather than treating an illustrative position as a measured ranking.
Diagnose missing or duplicate fetched metadata
URL mode reads the first matching HTML-head title and description declaration. It does not use a title inside SVG artwork or execute JavaScript to create missing metadata. If values are absent, they stay absent; the tool does not write a replacement summary from the body.
| Source finding | What to do next |
|---|---|
| Missing title | Check the page's title setting and template. A visible heading alone is not the HTML title element. |
| Missing description | Write an accurate summary in the page's metadata setting; do not assume text elsewhere is the declared description. |
| Duplicate titles or descriptions | Identify the template, plugin or component emitting each declaration and keep the intended source consistent. The preview shows the first one. |
| Shortened source metadata | Inspect the original value. The editor has capped its displayed text; the website itself was not modified. |
Source counts and warnings describe the fetched page. Editing the preview does not remove a duplicate tag from that page or prove its published source was repaired. Save chosen wording before loading the URL again, because another fetch replaces the editor's metadata with the newly retrieved values.
A failed fetch also does not show that Google cannot read the page. Check the public URL and access separately. The simulator inspects one delivered HTML response, not every rendered page version or crawler request.
Copy the chosen tags and verify the published page
Use Copy metadata HTML after reviewing the wording. It exports a title element and meta-description tag, escaping characters such as & and quotes for HTML. The copied code does not include the illustrative site name, query highlighting or a Google result. If your CMS expects plain title and description fields, enter the wording in those fields rather than pasting HTML tags into them.
Keep one intended title and description in the page's generated head. Copying does not update the website, and adding a second tag beside an existing declaration can create the duplicate you meant to fix.
- Choose the draft that accurately describes the page and remains clear in both preview layouts.
- Update the responsible CMS fields or template, then publish through your normal workflow.
- Use Meta Tag Analyzer to inspect what the published URL actually returns.
- Compare the source separately from any Google result you observe. Google may select other title text or a different query-dependent snippet after processing the page.
For wording alternatives, use the AI SEO Title Generator or AI Meta Description Generator, then review those drafts against the actual page. Neither a generated phrase nor a fitting preview guarantees a ranking or click-through improvement. Keep the chosen metadata and publication date in your own notes so later comparisons refer to a known change.