An on-page SEO checker helps you find problems in a page's metadata, structure, links, and technical settings. Screpy checks the URL you submit and groups the findings so you can investigate the page without starting with a full website crawl.
The useful outcome is a short list of justified improvements. A missing title, an accidental indexing restriction, and an intentionally empty image description call for different decisions. Use the report to understand what is on the page, then decide what needs to change.
How to use an on-page SEO checker
Choose the specific page you want to improve. Checking your homepage will not tell you whether a product page has the right title or whether a recently published article has an indexing restriction.
- Copy the full public URL, including
https://and the page path. For example,https://example.com/products/trail-backpack/represents one product page. - Paste it into the checker above and submit it. Review the reported URL and HTTP information before interpreting the other findings.
- Read the actual values shown for the title, description, canonical, and headings. Compare them with the page you intended to check.
- Note any unavailable checks. If the analysis cannot be completed, treat the result as unavailable rather than a completed audit.
Decide what the page is meant to do before changing anything: sell a product, explain a service, or answer a question. If you also need to inspect a tracking URL or another variant, submit that URL separately. One report is a starting point for one page; it does not establish the condition of every page on the domain.
What the report colors mean
The report uses colors and icons to make individual checks easier to scan:
- Green indicates a passing check. It confirms that check's condition, rather than the quality of the entire page.
- Amber marks a warning worth reviewing. The right response depends on the page and its purpose.
- Red marks an error to investigate. Read the associated finding to understand the cause and affected element.
These statuses are Screpy's audit results. They are not Google's assessment of where the page should rank. A title-length warning, for example, needs a readability review; it does not prove that the title is preventing indexing.
Start with findings that could stop the intended page from being accessed or indexed, then review the content and supporting elements. Keep informational or unavailable results separate from passing checks. When a metric is unavailable, you have no measurement to interpret—not a zero value or evidence that everything is fine.
Check access, indexing rules, and canonicals first
First ask whether this URL should appear in search. A public service page and a private account page should not necessarily have the same indexing settings. Change restrictions only when they conflict with the page's intended visibility.
For a page you want Google to index, check that it is accessible, returns a successful 200 response, and contains indexable content. These are Google's basic technical requirements, not a guarantee of inclusion. A successful response also deserves a content check: make sure the page actually contains the intended material rather than an error message.
Keep crawl permission and indexing permission distinct. A robots.txt rule controls crawling. A noindex directive tells Google to exclude a page, but Google must be able to crawl the page to discover that directive. If a public landing page was accidentally excluded, investigate the relevant rule before removing it. Use the Robots.txt Tester when the concern is crawl access. Use Noindex Checker to inspect the page’s HTML and HTTP directives, including their source and applicability to Google web search. For AI crawler rules, compare policies with AI Bot Access Tester. This checks robots.txt only and does not establish actual bot access, indexing or citations.
A canonical identifies the preferred version among duplicate or very similar pages. A tracking variant pointing to the clean URL may be correct; an unrelated product pointing to the homepage needs investigation. A missing canonical alone does not prove an indexing block, and a declared canonical does not force Google's choice. Keep your declared preference consistent with internal links and sitemap URLs, following Google's canonical guidance. The Canonical Tag Checker provides a focused next check when the declared URL or its target looks wrong.
Make the title and content useful to searchers
Metadata helps explain what someone will find. The page itself must then deliver on that explanation. Review both together instead of editing tags in isolation.
Write a clear title and description
A title should identify the page specifically. In a hypothetical store, Products | North Trail says little about one backpack. 30L Day Hiking Backpack | North Trail is more informative if that is the product actually offered. Use genuine attributes; adding “waterproof” to a product that is merely water-resistant would mislead buyers.
Treat length warnings as prompts to inspect clarity and truncation. Google sets no fixed title character limit and can generate title links from several page signals. Its title-link guidance favors descriptive, concise wording over repeated keywords and boilerplate.
Write the description as a useful summary of this page, with relevant details that distinguish it from other pages. Google may use page content instead and can show different snippets for different searches. There is also no fixed meta-description length limit; displayed snippets can be truncated to fit the device. See Google's snippet guidance.
Review headings and the actual content
The main heading should make the page's subject obvious, and section headings should help visitors find the answers they need. Check that the reported headings describe the content, rather than repeating the same phrase in every section.
For the backpack example, buyers may need capacity, dimensions, materials, intended use, and delivery or return details. For a service page, the essential answers will be different. Read the page with that visitor's task in mind.
Word counts and keyword lists can reveal what was detected, but they cannot establish whether the explanation is complete or trustworthy. Google explicitly states that it has no preferred word count. Add missing answers or useful evidence; avoid padding the page to satisfy a number.
Review links, images, and structured data in context
Links: Inspect the destinations and the text visitors use to reach them. “Backpack sizing guide” sets a clearer expectation than “click here.” Important navigation should use crawlable links with real destinations, following Google's link best practices. If a destination appears broken, verify it before changing the link. A list or count of links by itself does not establish that every destination works or that your internal linking is complete.
Images: Review the image's role before responding to an alt-text warning. A meaningful product photo needs an appropriate description; an image acting as the only label for a link or button needs text explaining the destination or action. A purely decorative image can correctly use alt="". That is different from omitting the attribute. The W3C alt decision tree explains these distinctions. Do not add repeated keywords to every image just to remove a warning. Also check whether important information in an image is available in readable page content.
Structured data: Finding markup is the start of a review, not proof that the page qualifies for a particular search feature. Check that the type fits the page, its information matches visible content, and the required properties for the intended feature are present. Follow Google's structured data guidelines and validate the applicable feature with the Rich Results Test. Correct markup still does not guarantee a rich result. Add schema to describe genuine content, rather than inventing ratings, products, or claims to obtain a different search appearance.
Turn the findings into a fix queue
For each finding, record the URL, the observed value, why it matters for this page, who will make the change, and how you will confirm completion. This gives a developer or content editor enough information to act without guessing what “improve SEO” means.
Here is a hypothetical audit of the backpack product page. These are example decisions, not results from a live Screpy check.
| Finding | Decision | Completion check |
|---|---|---|
noindex on the public product page |
Investigate first. If accidentally inherited from a template, remove it from this search-intended page. | Published page no longer declares noindex; verify Google can access the page. |
| Generic title: “Products” | Ask the content owner to write an accurate product-specific title. | New title identifies the product and matches the visible offer. |
| Tracking variant canonicalizes to the clean product URL | Keep it if both URLs represent the same content and the clean URL is the intended preference. | Declared target is correct and consistent with the site's chosen URL. |
Decorative background image has alt="" |
Keep the empty alternative if the image conveys no information and serves no control or link function. | Meaningful content and controls remain understandable without that image. |
The first row deserves attention before title polish because it conflicts with the page's intended visibility. The last two rows may require no code change. Record the decision anyway, so the same intentional setting is not repeatedly “fixed” in later audits.
Verify the fix and look beyond one page
After publishing a change, rerun the checker on the same public URL. Compare the relevant values with your original notes. Confirm that the update reached the published page, rather than assuming an edited CMS field is already visible to visitors. If the issue comes from a shared template, check another affected page as well.
For questions about Google's view, use Search Console's URL Inspection tool. Its live test examines the current page, while indexed data describes the version Google last processed. When essential content loads through JavaScript, inspect the tested page's rendered output. Look in indexed data for Google's selected canonical; a live test cannot predict that choice. A successful inspection does not guarantee indexing, and fixing an audit finding does not promise an immediate ranking change.
A single-page report also cannot establish whether other pages reuse the same title or whether this page has no incoming internal links. Those questions need wider site context. Use Screpy Website Audit to review related pages, repeated template issues, and links across a crawl. Start with the page-level problem, verify the correction, then expand the audit where the evidence calls for it.
To compare response codes and redirect chains across a list of pages, use the Bulk HTTP Status Checker.