Page Authority Checker

Fetch any URL and get an estimated 0-100 on-page score with a grade, built from 16 checks on HTTPS, speed, title, meta description, headings, content, links and canonical tags.

Enter the full URL including https:// — e.g. https://wikipedia.org/wiki/HTML

When a page isn't getting traction in search, the first question is whether the basics are even in place: a proper title, a meta description, headings, enough text, a canonical tag, sharing tags, a fast and clean response. Checking all of that by viewing the source is slow. The Page Authority Checker fetches one URL, runs 16 on-page checks in four groups and turns them into an estimated score from 0 to 100 with a letter grade, so you can see in a few seconds which signals are missing.

It is built for auditing your own pages: before publishing, after a redesign or CMS migration, or when a page has been sitting in Search Console as "Crawled - currently not indexed" and you want to rule out technical gaps. It is not a backlink tool, and that matters for how you read the number.

What this score is, and what it is not

"Page Authority" was popularised by Moz, whose PA score predicts ranking strength mainly from links pointing at a page. This tool has no link index, so it does not try to copy Moz's number. Every point here comes from the page's own HTML and how the server responds. If you need link-based metrics, use Moz Link Explorer or a similar backlink database; for a quick count of links to a site, try our Backlink Checker.

How to check a page

  1. Paste the full address into Enter Page URL. If you leave out https://, the tool adds it.
  2. Click Check Authority or press Enter.
  3. Read the dial (score out of 100), the grade badge and the one-line verdict, then the four cards below it: Technical, Title & Meta, Content Quality and Links & Canonicals. Each card shows its own score and the raw values found, such as title length in characters or the number of links.

The page is fetched by Toolspedia's server, not by your browser, using the user agent ToolsBot/1.0, following redirects, with a 15-second time limit. Private or local addresses are refused.

How the points are awarded

Group (weight)Checks and points
Technical (20%)HTTPS 30; final status 200 gives 40 (another status below 400 gives 20); response under 1 s gives 30, under 2 s 20, under 4 s 10
Title & Meta (25%)Title of 20-70 characters 35 (any other title 20); meta description of 50-160 characters 35 (other length 20); og:title 20; twitter:card 10
Content Quality (30%)H1 20; H2 10; over 300 words 20, over 800 words 15 more, over 1,500 words 10 more; at least one image 10; an image with alt text 10; structured data 5
Links & Canonicals (25%)3 or more links 30; 10 or more 20 more; 2 or more absolute (http/https) links 20; canonical tag 30

Each group is scored out of 100, multiplied by its weight and added up, then rounded. Grades: A is 80 or more, B 65-79, C 50-64, D 35-49 and F below 35.

Worked example: an MDN reference page

We ran the tool on MDN's page for the HTML <meta> element. It returned a score of 85, grade A, with this breakdown:

  • Technical 100: HTTPS, status 200, 0.31 s response, 183.8 KB.
  • Title & Meta 65: the 47-character title earned 35; the meta description is 193 characters, over the 160 limit, so it earned 20 instead of 35; there is no og:title (0); a Twitter Card is present (10).
  • Content Quality 80: H1 and H2 present (30), well over 1,500 words (45), structured data (5), but no <img> tags, so both image checks scored 0.
  • Links & Canonicals 100: 455 links, 20 external, canonical tag present.

The arithmetic: 100 x 0.20 + 65 x 0.25 + 80 x 0.30 + 100 x 0.25 = 20 + 16.25 + 24 + 25 = 85.25, rounded to 85. For contrast, the bare placeholder page at example.com scored 25 (F): fast and on HTTPS, but a 14-character title, no meta description, no sharing tags, 48 words and no links or canonical found.

The example also shows that a high-quality page can lose points for choices that are fine in context: a text-only reference page has no reason to add images. Treat each lost point as a question, not an order.

Reading your result

  • 80 and above: the on-page basics are covered. If the page still doesn't rank or get indexed, look at content depth, search intent, internal links and backlinks.
  • 50-79: one or two groups have gaps. Open the lowest card first; a missing meta description, og:title or canonical tag costs a lot and takes minutes to fix. The Meta Tag Generator writes the title, description and Open Graph tags in one go.
  • Below 50: usually a thin or template-like page, a page whose content loads only through JavaScript, or a fetch problem. Check the HTTP status and word count values before anything else.

Limits and edge cases

  • Raw HTML only. The tool reads what the server sends and does not run JavaScript, so headings and text injected by a client-side app may show as missing.
  • Word count is generous. It counts all text left after HTML tags are stripped, which includes inline script and style code, navigation and footer text. Use the Word Counter on your article text for the real length.
  • Presence, not correctness. A canonical tag pointing at the wrong URL, or structured data with errors, still scores. Any mention of schema.org counts as structured data.
  • Byte-based lengths. Title and description lengths are counted in bytes as written in the HTML, so accented characters, non-Latin scripts and entities such as &amp; make them look longer than they appear in search results.
  • Response time is one sample from our server, including redirects. It is not a Core Web Vitals measurement; use the Website Speed Checker or Google's PageSpeed Insights for that.
  • Blocked fetches. Sites behind bot protection may return an error page or a 403, which drags every group down. That reflects the firewall, not the page.

Compared with other approaches

Moz PA, Ahrefs URL Rating and Semrush Authority Score measure link strength from large crawls and are the right tools for sizing up competitors. Full crawlers such as Screaming Frog check the same on-page items across a whole site, render JavaScript and validate canonicals, but need installing and configuring. This checker sits in between: one URL, no sign-up, a transparent formula you can recalculate yourself. Google's own guidance on title links and snippets sets no fixed character limits, so treat the 20-70 and 50-160 ranges as practical targets rather than rules. For a whole-domain view, use the Domain Authority Checker.

Frequently Asked Questions

No. Moz PA is mainly based on links pointing to a page. This tool has no link index and scores only the page's own HTML and server response, so use it to fix your pages, not to compare link strength.

Four groups are each scored out of 100: Technical (20% weight), Title and Meta (25%), Content Quality (30%) and Links and Canonicals (25%). The weighted scores are added and rounded. A is 80 or more, B 65-79, C 50-64, D 35-49 and F below 35.

The tool reads the raw HTML your server sends and does not run JavaScript. If your headings and text are rendered by a client-side framework, they will not be counted. Server-side rendering or prerendering fixes this for crawlers too.

Full points need a description of 50-160 characters and a title of 20-70 characters. Lengths are counted in bytes as written in the HTML, so accented letters, non-Latin text and HTML entities can push the count over the limit.

Open the card with the lowest score. A missing meta description, og:title tag or canonical tag costs the most points and takes minutes to add. Image points only matter if the page genuinely benefits from images.