You do not need to buy a subscription to find out whether your service page has a broken link or tells search engines to stay away. But you do need to know what a free SEO report is actually checking.
A page can pass its technical checks and still give a visitor no reason to contact you. It can also show a warning that is perfectly intentional, such as keeping an account page out of search.
Here is how to use a free checker to find a useful next job, without treating every red label as an emergency.
Start with the page a customer needs
Choose one public page: a service description, a product page, or an article that answers a real buying question. Use the full live address, not a draft preview or the address of your website editor.
For example, a photographer might start with /wedding-photography, rather than checking the homepage and assuming the findings apply everywhere.
Before running anything, open that address in a private browser window. Confirm you can read it without signing in. Check that the main text, images and enquiry button work on your phone too.
That last check is yours to do. An HTML checker cannot tell whether a booking form is frustrating or the photographs take too long to appear.
Run one check and read the two columns separately
Open SEO Dispatcher's free SEO checker, paste the page address, and run the check. The report reads the HTML and headers the public server sends; it does not load the page like an interactive browser.
The checklist separates Found from Result. That is an important distinction:
- Present means the tool detected something. It does not mean the value is correct.
- Missing means it was not detected in the inspected response. Content added later by JavaScript may need a separate rendered-page check.
- Needs review means you should inspect the evidence before deciding on a change.
- Optional or Not needed is not a failed SEO requirement.
- Not checked means there is no conclusion. Do not count it as a pass.
Expand a row to see the current value, affected address, explanation and proposed action. Fix the problem in that row, not the label itself.
Check access before editing the wording
Start with the page response and indexing instructions. An error response, a login requirement, or an unintended noindex instruction matters more than polishing a description.
noindex asks search engines not to include the page. A robots.txt rule controls whether a crawler may fetch it. These are different settings; blocking a page can prevent Google from reading its noindex instruction. Google's noindex guidance explains the difference.
Keep exclusions on private or account pages when they are intended. Investigate an exclusion on a public service page you want customers to find.
The report can identify an observed instruction. It cannot establish that Google has indexed the page. For that answer, the website owner needs Search Console URL Inspection. You do not need to connect Search Console to SEO Dispatcher to use the free checker.
Look at the actual title, description and canonical
A title being present is a low bar. Read it as a person deciding which result to open.
For a hypothetical wedding photographer, “Home” says very little. “Wedding Photography in Bristol | Willow Studio” tells the visitor what is offered and where. Use a location only if the business genuinely serves it.
A description should add a useful detail, not repeat the title three times. “See full wedding galleries, what each package includes, and how to check your date” gives the reader a reason to visit, provided the page delivers those things. Google may choose a different search snippet; the description is not a promise about the final result. See Google's snippet guidance.
Next, inspect the canonical: the preferred address for equivalent versions of a page. A service page pointing to the homepage deserves attention, but a different target is not automatically wrong. A deliberate duplicate may correctly point to another version.
For a page you want to stand on its own, check that its preferred address, sitemap entry and internal links agree. Do not change an established URL just to make it contain a keyword.
Decide what each finding actually needs
Use the evidence to choose a small, specific action. Here are illustrative cases, not results from a customer website:
| Finding | Decision to make | Useful next action |
|---|---|---|
| Public service page returns an error | Is the page supposed to exist? | Repair the page or remove outdated links; rewriting its text will not fix the response. |
| Article's canonical points to the homepage | Is this really duplicate content? | If not, correct the article's preferred URL in the website settings or template. |
| Title says only “Services” | Can a visitor identify the offer? | Name the actual service and business clearly. |
| An image has no alt attribute | Does it convey information or decorate the page? | Describe useful visual information; use an empty alt attribute for a decorative image. |
| JSON-LD is missing | Would a suitable type describe this page? | Investigate the page type first. Missing markup alone does not mean the page cannot rank. |
The checker also inspects a small sample of internal link destinations. If it finds a missing destination, open that specific link and confirm what it should lead to. It has not checked every link on your website.
Do the part a checklist cannot do
Now read the page without looking at the report. Ask:
- Would a first-time visitor understand what this is for?
- Does it answer the question suggested by the title?
- Are claims, examples, prices and availability accurate?
- Does the reader have a sensible next step?
If the wedding page has good metadata but no galleries, package details or way to enquire, those omissions are worth fixing. A green technical checklist does not make an incomplete offer useful.
This is where SEO Dispatcher's paid workspace can help with a different job: review connected search evidence, prepare a relevant article or update, and publish approved content in your site's Markdown or MDX format through GitHub. It does not automatically repair a website template, canonical setting or broken form.
Save one clear task and verify the change
Copy the affected URL, current value and intended change into a note for whoever maintains the site. For example:
The wedding service page is public, but its canonical points to the homepage. Please confirm it is a distinct page and, if so, set the preferred address to the existing service URL. After publishing, check the live response rather than the editor preview.
That task has a location, a reason and a way to verify the fix.
Plan your checks carefully. SEO Dispatcher's free allowance is three accepted runs total per user and domain across all tools, with no reset. Signing in reveals more evidence from the same report, not more runs. Accepted checks that fail to fetch data still use an attempt; opening a saved report within its 24-hour availability does not use another one. Anonymous users on a shared network may share an allowance.
Spend a run on the page you have actually changed, not on every spelling of the same address. After deployment, open the live page, confirm the expected value, and use the appropriate follow-up check. Technical eligibility still does not guarantee indexing or a ranking, as Google's technical requirements make clear.
The result you want is not “everything is green.” It is “we found a real problem, made the right change, and checked that it reached the website.”