Helpful Content Checker
Fetch any URL and see which of the signals behind Google's helpful content guidance the page actually shows: author, dates, sourcing, content-to-template ratio, ad load and affiliate disclosure. Ten checks on every page, two more when it carries affiliate links, each with the method it used, and no invented score.
Short answer
A helpful content checker reads a page and reports which of the trust and effort signals Google's helpful content guidance points at are present: who wrote it, when it was published and last updated, what it cites, how much of it is content rather than template, and whether its monetisation is disclosed. It does not produce a helpful content score, because Google has never published one and the helpful content system stopped being a separate classifier in March 2024, when it was folded into core ranking. Most of the guidance is a list of self-assessment questions about your own writing that no tool can answer. This one answers the part that is readable in HTML, names the method it used for each result, and leaves the judgement to you.
What a tool can know about this, and what it cannot
Google's helpful content guidance is roughly thirty questions, and they are written for a person assessing their own site. "Does the content provide original information?" and "Does it leave the reader feeling they need to search again?" are good questions with no HTML representation whatsoever.
So any tool in this category has to pick a lane. It can invent a score from proxies and present it confidently, or it can check the subset that is actually readable and say so. This one does the second.
| The guidance asks | Readable? | What this tool does |
|---|---|---|
| Is there a byline, and who is behind it | Yes | Reads schema, rel=author and byline markup |
| Is the content kept up to date | Yes | Reads publish and modified dates |
| Is there clear sourcing | Yes | Counts outbound citations inside the main content |
| Do ads distract from the content | Partly | Counts ad slots in the served HTML |
| Is the content original | No | Nothing. Reported as out of scope rather than guessed |
| Does it leave the reader satisfied | No | Nothing. This is what analytics is for |
| Was it written for people or for search engines | No | Nothing. No tool can tell, including this one |
There is no helpful content score
Nothing on a page corresponds to one, and since March 2024 there is no separate system to score against. A tool that hands you 72/100 has built that number from proxies and given it a precision it does not have.
What actually happened to the helpful content update
The naming causes most of the confusion here, so it is worth being precise about the sequence.
- August 2022: the helpful content update launched as a separate, site-wide classifier. A signal applied to the whole domain rather than the page, which is why sites saw everything move at once.
- September 2023: a second run, notable for how many sites reported losses they could not attribute to anything they had changed.
- March 2024: Google announced the system had been integrated into core ranking and would no longer run as a standalone update. There is no discrete helpful content update to be hit by any more.
- Since then: the guidance document survives and is still the clearest statement of what Google says it wants. The classifier it was written to explain does not exist as a separate thing.
The practical consequence is that waiting for a recovery event is waiting for something that no longer happens. What is left is the guidance, and the parts of it that show up in your markup, which is what this page checks. The wider question of which pages deserve the effort is what the on-site SEO checklist works through.
The signals, and why each one is here
Grouped by the question they answer. Each result names the method that produced it, because a finding you cannot argue with is a finding you have to take on trust.
| Group | Signal | Read from |
|---|---|---|
| Attribution | Names an author | JSON-LD author, rel=author, or byline class and itemprop |
| Attribution | Author links to a bio | The href on the byline |
| Attribution | States a publish date | datePublished, or a <time datetime> element |
| Attribution | States a last-updated date | dateModified, or a time element marked updated |
| Attribution | Declares article schema | Article, BlogPosting, NewsArticle or TechArticle |
| Sourcing | Cites sources outside itself | External links inside the main content only |
| Substance | Has enough copy | Word count against the named content boundary |
| Substance | Is mostly content | Content words as a share of whole-page words |
| Substance | Breaks into sections | H2 to H6 inside the main content |
| Monetisation | Keeps advertising off the content | Ad slot markup in the served HTML |
| Monetisation | Marks up affiliate links | rel on links with tracking parameters or cloaking paths |
| Monetisation | Discloses the relationship | Disclosure wording anywhere in the document |
The last two appear only when monetised links are found, so most pages see ten. Two of these are worth explaining. Outbound links are counted inside the main content only, because a template footer linking to four social networks is not sourcing, and a single total would describe your theme rather than your article. And the content ratio matters more than the word count: 400 words inside a 500-word page is an article, while the same 400 inside a 4,000-word page is an article buried in navigation. Attribution is the half of this that overlaps E-E-A-T, which is a set of rater guidelines rather than a score, for the same reason nothing here is one. The page word counter uses the same boundary and shows the workings in more detail.
How to use the results
Seven steps, ordered so the cheap fixes and the legal ones come before the judgement calls.
- 01
Run a page that earns impressions
Signals are cheap to add and only pay on pages people already reach. Start with the URLs that show up in Search Console rather than working through the site in menu order.
- 02
Read the attribution block first
Author, publish date and updated date are the three cheapest things on this list to fix and the three Google's own guidance names most directly. They are usually one template change rather than an edit per page.
- 03
Ignore the signals that do not apply
A pricing page has no author and a changelog has no citations, and neither is a defect. This tool reports what it found and does not decide which findings apply to your page type.
- 04
Check the content-to-template ratio, not the word count
The word count is context. The ratio tells you whether the page is an article inside a template or a template with a little writing in it, and only the second one is a real problem.
- 05
Add sourcing where you made a claim
Clear sourcing is one of the very few things in the guidance a machine can look for. If the page states figures, dates or quotes and links to nothing, that is the gap worth closing.
- 06
Fix the affiliate markup before anything else
An undisclosed affiliate link is a legal problem before it is an SEO one. If the tool found monetised links with no rel and no disclosure, that outranks everything else on this page.
- 07
Stop treating the output as a score
Google publishes no helpful content score, and since March 2024 there is no separate classifier to score against. Use the list to find things worth adding, not to chase a number.
Most of what this finds is a template property rather than a page property, so a fix usually lands across every page using that layout. Once the signals are in place, the schema validator checks the markup carrying them is valid, and the heading analyzer covers the section structure this page only counts.
What this checker reports
Twelve readable signals
Ten on every page, two more when it carries affiliate links
The method beside every result
Where each finding was read from, so it can be checked rather than trusted
Author detection three ways
JSON-LD, rel=author and the byline class conventions the major themes ship
Nested and @graph schema
Yoast and Rank Math ship one graph node; a top-level read sees nothing at all
Content boundary, named
Word counts against main, role=main, the longest article, or body minus furniture
In-content sourcing only
Template outbound links are excluded, so the count describes the article
Affiliate and ad markup
Tracking parameters, cloaking paths, rel values and disclosure wording
No invented score
A count of what was found, because Google publishes no helpful content score
What this reads, and what it cannot
Frequently asked questions
What is a helpful content checker?
A tool that fetches a page and reports which of the signals behind Google's helpful content guidance the page actually shows: who wrote it, when it was published and updated, what it cites, how much of it is content rather than template, and how it is monetised. It does not judge whether the writing is helpful, because no tool can read a page and know that.
Does this give me a helpful content score?
No, and any tool that does is inventing the number. Google has never published a helpful content score, and the helpful content system stopped being a separate classifier in March 2024 when it was folded into the core ranking systems. There is nothing on a page that corresponds to a score, so this tool reports a count of signals found and says which ones.
Is the helpful content update still a thing?
The guidance is, the standalone system is not. Google ran the helpful content update as a separate site-wide classifier from August 2022, then announced in March 2024 that it had been integrated into core ranking. That is why there is no longer a discrete recovery event to wait for: the signals are assessed continuously alongside everything else.
What signals does this tool actually read?
Twelve, in four groups, of which ten apply to every page. Attribution: author name, a link to an author bio, publish date, last-updated date and article schema. Sourcing: outbound citations inside the main content. Substance: main content word count, content-to-template ratio and subheading count. Monetisation: ad slot count on every page, plus affiliate link markup and disclosure wording, which appear only when monetised links are found.
Why does it report signals rather than pass and fail?
Because none of them is a rule. An undated reference page is fine, a pricing page with no byline is fine, and a documentation page with no outbound citations is fine. Reporting these as failures would tell you to add furniture to pages that do not need it, which is the exact behaviour the guidance was written to discourage.
How many words does a page need?
None in particular. Google has never published a minimum and has said repeatedly that word count is not a ranking factor. This tool uses 300 words only as the point below which a page rarely answers the question that brought someone to it, and it prints the number next to the boundary it used so you can judge it yourself.
What is the content-to-template ratio?
The share of the page's words that sit inside the main content rather than in the navigation, header, sidebar and footer. It matters more than the raw count: 400 words of article inside a 500-word page is a real article, and 400 words inside a 4,000-word page is an article buried in furniture.
Does an author byline affect rankings?
Not as a direct signal, and Google has said there is no E-E-A-T score. It matters because the quality rater guidelines ask raters to find out who is responsible for a page, and because a reader deciding whether to trust advice asks the same question. A byline that links to a real bio answers it; a name in grey text does not.
Why does it flag affiliate links without a rel attribute?
Because Google asks that paid and affiliate links carry rel="sponsored" or rel="nofollow", and a monetised link with neither passes an endorsement that was bought. The tool detects these from tracking parameters and the cloaking paths that affiliate plugins use, so it will miss a link that hides its parameters server-side.
Does it detect AI-written content?
No, and it will not pretend to. AI detection does not work reliably, Google's position is that it rewards quality regardless of how content is produced, and a tool guessing at authorship would produce confident answers with nothing behind them. What this checks is whether the page shows its work, which is a question with an answer.
Why do the results differ from what I see in my browser?
It reads the HTML your server returns, before any JavaScript runs, which is what a crawler reads first. A byline, a date or an ad slot injected by client-side code is absent here. If a signal you can see in the browser is missing from this report, it may also be missing from what Google indexed on its first pass.
My page scores badly. Will it start ranking if I fix these?
Probably not on its own, and it would be dishonest to suggest otherwise. These signals are things a page shows rather than reasons a page ranks. Adding a byline to a page that does not answer its query changes nothing. They are worth doing because they are cheap, and because their absence is one of the things a rater or a reader notices first.
Can I check a whole site at once?
Not with this tool. It reads one URL in depth, which is a different job from the bulk tools that read one tag across a hundred URLs. Run it on a page that represents a template, because most of what it finds is a template property rather than a page property.
Can I export the results?
Yes, as CSV, with the group, the signal, the verdict, what was found, the method used to find it and why the guidance cares. The method column is there so a result can be argued with rather than taken on trust.
Other on-page SEO tools
Canonical Tag Checker
Validate canonical tags for self-referencing, protocol mismatches, trailing slash conflicts, noindex conflicts, and og:url consistency.
Use toolHreflang Validator
Validate hreflang tags for international SEO: self-referencing, return tags, x-default, language codes, and duplicate detection.
Use toolSchema & JSON-LD Validator
Validate structured data markup: required properties, date formats, nested entities, and JSON syntax. Supports all major schema types.
Use toolMeta Tag Checker
Check title tags, meta descriptions, Open Graph tags, Twitter cards, canonical URLs, robots directives, and viewport settings.
Use toolMeta Tags Generator
Write the title, description, and social share tags every page needs. Live character counts plus previews of how it will look in Google and on social.
Use toolKeyword Density Checker
See which words and phrases your copy actually leans on. Single word, two word and three word counts with density and first-mention position.
Use toolSERP Snippet Preview
See your title and meta description the way Google renders them, measured in pixels. Desktop and mobile, with the exact character your snippet is cut at.
Use toolURL Slug Generator
Turn a list of page titles into clean, readable URL slugs. Accents transliterated, filler words optional, and duplicates caught across the whole list.
Use toolAnchor Text Generator
Build branded, partial, long tail and naked URL anchor variations for any page, then audit the anchors you already have against a natural distribution.
Use toolReadability Checker
Score any text on six readability formulas at once, then see which sentences are dragging the grade up. Passive voice and long sentences broken out separately.
Use toolPage Word Counter
Count the words on any URL, with the body copy separated from the nav, header and footer. Unique words, reading time, paragraphs and the heading outline.
Use toolImage Alt Checker
Audit the alt text on every image on a page. Missing attributes kept apart from decorative alt="", plus image links with no name, filenames used as descriptions and duplicates.
Use toolOpen Graph Preview
Paste your meta tags and draw the card each platform renders, cut where it really cuts. Works on staging and on tags you have not deployed yet.
Use toolTwitter Card Validator
X retired its own validator in 2022. Check twitter:card on a live URL, see which tags X reads through the Open Graph fallback, and prove the image loads.
Use toolOpen Graph Checker
Fetch a live URL and read its og: tags the way a scraper does, then check the card image actually loads rather than only that the tag exists.
Use toolHeading Analyzer
Read the H1 to H6 outline of any URL and find the skipped levels, empty headings and duplicate labels, with the page's own headings separated from its template.
Use toolBulk Title Tag Checker
Check up to 100 title tags at once, measured in pixels rather than characters, and find the duplicates across a set that no single-URL checker can see.
Use toolBulk Meta Description Checker
Check up to 100 meta descriptions at once, measured in pixels, and find the duplicates, empty tags and descriptions that just repeat the title.
Use toolRead up on on-page content
A tool tells you what is wrong. These explain what to do about it.
Ten signals on one page, and four thousand pages
Most of what this finds is a template property, so the fix lands everywhere at once. Knowing which templates are worth fixing first is the harder question. CrawlRaven joins your crawl to Search Console and GA4, so the pages missing these signals come back ranked by the impressions already sitting behind them.