Content and structure
What the page announces and how it is built: title, description, heading hierarchy, amount of text. This is where a search and your page either match or do not.
Free tool, instant result
What does Google understand about your site?
Enter its address. We read the page the way a search engine does: title, structure, content, indexing, sharing, technical setup. Twenty-eight checks, a grade from A+ to F, and what to fix.
- The page is read live, exactly as served
- Every point explained, with what to do
- Full report once your account is open
What we examine
The page is requested from your server the way a crawler would, then read: tags, structure, visible text, links, structured data, robots.txt and sitemap. No third-party service, no API key. Whatever we could not observe is marked “not tested” rather than guessed.
Indexing
What decides whether the page can appear at all: response code, permissions given to crawlers, canonical address, sitemap. One of these wrong and the rest is wasted.
Sharing and rich results
What social networks, messaging apps and rich results receive: share preview, structured data, icon. Invisible on the page, very visible everywhere else.
Technical and mobile
Phone rendering, declared language, internal linking, compression and response time. What makes a well-written page a well-served one.
How the grade is calculated
Every check carries a fixed weight. A failure removes all of it from its family, a reservation removes half, and a check that does not apply leaves the calculation instead of weighing on the grade. The overall grade is the weighted average of the four families: content counts for 35%, indexing for 30%, technical for 20%, sharing for 15%. A page that forbids its own indexing sees that family drop to zero, whatever its other tags say.
- A+Nothing Google expects is missing.
- ASolid, bar one detail.
- BSound, with points to revisit.
- CVisible gaps in several families.
- DBasic signals are absent.
- EThe page is poorly understood and poorly shared.
- FNeeds rework, starting with indexing.
Frequently asked questions
Where do these results come from?
From your page, requested live from your server, then read the way an indexing crawler would. We add two requests, for robots.txt and the sitemap. No third-party service is involved.
How is this different from the site audit?
The site audit looks at security first: certificate, headers, encryption, plus a dozen SEO points along the way. This tool does SEO only, but twice as deeply: heading structure, amount of text, structured data, sitemap, translated versions.
Does it tell me my position in Google?
No, and nobody can tell you honestly from a single request: a position depends on the search, the place and the person. This audit answers something more useful for acting: what your page allows or prevents.
How do I fix what it reports?
Most points live in the page template: title, description, headings, share tags. The sitemap and robots.txt live with your host or your publishing tool. Every line of the report says what is missing and why it matters.
A site that ships with all of this in place
Sites published on Wobelio arrive with titles, descriptions, sitemap, structured data and mobile rendering already in order. There is nothing to configure to earn the grade.