# PageRank Ninjaz — full content > See how badly your site is doing in Google, in AI answers, and on the map. Then fix it. > Last updated: 2026-09-10 PageRank Ninjaz is a free website checker. You give it one web address. It returns three scores out of 100 — SEO, AEO and GEO — with every one of its 60 tests graded pass, warning or failure, the evidence for that grade, and a plain-English fix. No login, no card, 3 checks a day per visitor. ## The three scores | Score | The question it answers | Tests | |---|---|---| | SEO | Can Google find, read and rank this page? | 38 | | AEO | Will an assistant read this page out as the answer? | 11 | | GEO | Will an AI answer cite this page by name? | 11 | ## Scoring rule Each test carries a published weight. A pass earns the whole weight, a warning half, a failure none. The score is earned divided by available, as a whole number out of 100. A test that cannot run (a provider outage, or a row awaiting live rank data) leaves the denominator entirely rather than counting as zero, so an outage can never make a site look worse than it is. ## Pages ### Free website checker: SEO, AEO and GEO in one report https://pagerankninjaz.com/check Enter a web address and get three scores in seconds: how you do in Google (SEO), as the spoken answer (AEO), and inside AI answers (GEO). No login. Paste your address. In about 30 seconds you get three scores, every test graded, the evidence, and how to fix each one. No login, no card. ### Free SEO checker https://pagerankninjaz.com/free-seo-checker Free SEO checker with no signup: title, description, headings, schema, robots.txt, sitemap, speed, security and 30 more tests, each with how to fix it. Enter a page. We run 38 tests the way Google sees it, grade each one, show the evidence, and tell you how to fix it in plain English. ### Free AEO checker: are you the answer? https://pagerankninjaz.com/free-aeo-checker Free Answer Engine Optimization checker: direct-answer paragraph, question headings, FAQ schema, readability, entity clarity and voice-ready NAP, graded with fixes. Answer engines lift one paragraph and read it aloud. This checks whether your page gives them one, and shows how to write it. ### Free GEO readiness checker: can AI cite you? https://pagerankninjaz.com/free-geo-readiness-checker Free Generative Engine Optimization check: AI crawler access for 14 bots, llms.txt, structured data depth, content depth and citability, with generated fixes. ChatGPT, Google AI Overviews, Perplexity and Gemini only cite what they can read and trust. This checks the fourteen crawlers, llms.txt, your schema and your paragraphs. ## What the checker looks for ### Free website checker: SEO, AEO and GEO in one report #### What do SEO, AEO and GEO mean? They are three different ways of being found, and a page can be excellent at one and invisible in the other two. SEO is the blue links: can Google crawl this page, understand it, and rank it. That is the oldest of the three and still the largest share of most sites' traffic, which is why 38 of our 60 tests sit there. AEO is being the answer rather than a result. A featured snippet, a People-also-ask box or a voice assistant lifts one paragraph and reads it out. Pages that win those are written for it: a direct answer of roughly 40 to 60 words near the top, headings phrased as the question a person would ask, and facts in lists or tables that a snippet can pick up whole. GEO is being cited inside an AI answer. That requires two things in order: the AI vendors' crawlers must be allowed in, and once in, the page has to be quotable. We check 14 named AI crawlers, look for llms.txt, and count how many of your paragraphs are self-contained enough to be lifted with a number in them. | Score | The question it answers | Tests | Heaviest single test | |---|---|---|---| | SEO | Can Google find, read and rank this page? | 38 | Mobile speed (weight 6) | | AEO | Will an assistant read this page out as the answer? | 11 | Question headings (weight 10) | | GEO | Will an AI answer cite this page by name? | 11 | Structured data depth (weight 10) | #### How is a score actually calculated? Every test carries a published weight. A pass earns the whole weight, a warning earns half, a failure earns nothing, and the score is what you earned divided by what was available, rounded to a whole number out of 100. There are 60 tests in a full report. Nothing is averaged from a black box, so the same page checked twice gets the same number twice. A test that cannot run does not quietly cost you points. If the speed provider is unreachable, that row is marked not-available and its weight leaves the denominator entirely, so a provider outage cannot make your site look worse than it is. Rows that need live rank data or a paid API are marked coming, and they are excluded the same way rather than sitting at zero. Weights are not equal because the fixes are not equal. A missing title tag is worth 8 and takes two minutes. Question headings are worth 10 on the AEO side because they are the single strongest signal that a page was written to be quoted. Minifying CSS is worth 1, because in 2026 it almost never changes an outcome on its own. | Score | The question it answers | Tests | Heaviest single test | |---|---|---|---| | SEO | Can Google find, read and rank this page? | 38 | Mobile speed (weight 6) | | AEO | Will an assistant read this page out as the answer? | 11 | Question headings (weight 10) | | GEO | Will an AI answer cite this page by name? | 11 | Structured data depth (weight 10) | #### What should I fix first? Work down by weight, not down the page. The report sorts the worst rows to the top for exactly this reason: three fixes worth 10 each move a score more than fifteen fixes worth 1. Most sites we check have between 4 and 8 failing rows, and two or three of them account for most of the lost points. Read the evidence line before you change anything. Each failing row prints what we actually saw, such as the byte count of the HTML, the exact headings we found, or the crawler that returned a 403. If the evidence does not match your page, you are looking at a cached copy or a different URL, and the fix is to check the address rather than to edit the site. - Fix the heaviest failing row first: the report already puts it at the top. - Re-check after each change. Every check is kept, so the two runs sit side by side. - Ignore any row marked coming: it is excluded from the score, not counted against you. - Treat warnings as half-marks, because that is exactly what they are worth. #### What are the limits of this check? This is one fetch of one page, not a crawl of a site. It reads the HTML the server returns, the response headers, the robots file, the sitemap and the structured data, and it asks a speed provider for the mobile performance of that same address. It does not log in, it does not run your checkout, and it does not see pages that are not linked from the one you gave us. The score is an estimate against a published rule set, not a prediction of where you will rank. Ranking depends on competitors, links and history that no single-page check can see. What this is good for is the opposite direction: it tells you, with evidence, which of the things under your control are currently wrong, and roughly how much each one is worth. The free check runs 3 times a day per visitor and keeps every run from the first one, so a site you check today can be compared with the same site in a month. There is no login and no card. An account exists for people who want the same 60 tests run for them on a schedule and kept in one dashboard. #### Where do these rules come from? The SEO rows follow documented behaviour rather than folklore: title and description handling, canonicals, robots directives, sitemaps and mobile-first indexing are all described by Google in public. The speed row uses Google's own PageSpeed Insights, which is the same Lighthouse engine that reports Core Web Vitals, so the number you see here is the number Google's tool reports. The structured-data rows validate against schema.org types, and the AI-crawler rows check the user agents each vendor publishes for their own bots. Where a rule is genuinely contested, such as how much llms.txt matters today, the row carries a smaller weight and says plainly what it is testing, instead of pretending the industry has settled it. - Google Search Central, the documentation for how the crawler and index behave. - PageSpeed Insights and Lighthouse, for the mobile performance score. - Schema.org, for the structured-data vocabulary. ### Free SEO checker #### What does the SEO check actually look at? It reads the page the way a crawler does and grades 38 things in four groups. The basics are the ten that decide whether a page can rank at all: title, meta description, one H1, heading order, image alt text, canonical, viewport, indexability, the link ratio and the language declaration. The advanced group covers the twelve that separate a maintained site from an abandoned one, including the sitemap, robots directives, structured data, OpenGraph tags, the www and https redirect chain, freshness signals and broken internal links. The performance group is seven rows led by mobile speed, and security is four, led by whether the site is served over https at all. - Basics: 10 tests - Advanced: 12 tests - Performance: 7 tests - Security: 4 tests - Rank, AI and local: 5 tests #### How is a score actually calculated? Every test carries a published weight. A pass earns the whole weight, a warning earns half, a failure earns nothing, and the score is what you earned divided by what was available, rounded to a whole number out of 100. There are 60 tests in a full report. Nothing is averaged from a black box, so the same page checked twice gets the same number twice. A test that cannot run does not quietly cost you points. If the speed provider is unreachable, that row is marked not-available and its weight leaves the denominator entirely, so a provider outage cannot make your site look worse than it is. Rows that need live rank data or a paid API are marked coming, and they are excluded the same way rather than sitting at zero. Weights are not equal because the fixes are not equal. A missing title tag is worth 8 and takes two minutes. Question headings are worth 10 on the AEO side because they are the single strongest signal that a page was written to be quoted. Minifying CSS is worth 1, because in 2026 it almost never changes an outcome on its own. | Score | The question it answers | Tests | Heaviest single test | |---|---|---|---| | SEO | Can Google find, read and rank this page? | 38 | Mobile speed (weight 6) | | AEO | Will an assistant read this page out as the answer? | 11 | Question headings (weight 10) | | GEO | Will an AI answer cite this page by name? | 11 | Structured data depth (weight 10) | #### What should I fix first? Work down by weight, not down the page. The report sorts the worst rows to the top for exactly this reason: three fixes worth 10 each move a score more than fifteen fixes worth 1. Most sites we check have between 4 and 8 failing rows, and two or three of them account for most of the lost points. Read the evidence line before you change anything. Each failing row prints what we actually saw, such as the byte count of the HTML, the exact headings we found, or the crawler that returned a 403. If the evidence does not match your page, you are looking at a cached copy or a different URL, and the fix is to check the address rather than to edit the site. - Fix the heaviest failing row first: the report already puts it at the top. - Re-check after each change. Every check is kept, so the two runs sit side by side. - Ignore any row marked coming: it is excluded from the score, not counted against you. - Treat warnings as half-marks, because that is exactly what they are worth. #### What are the limits of this check? This is one fetch of one page, not a crawl of a site. It reads the HTML the server returns, the response headers, the robots file, the sitemap and the structured data, and it asks a speed provider for the mobile performance of that same address. It does not log in, it does not run your checkout, and it does not see pages that are not linked from the one you gave us. The score is an estimate against a published rule set, not a prediction of where you will rank. Ranking depends on competitors, links and history that no single-page check can see. What this is good for is the opposite direction: it tells you, with evidence, which of the things under your control are currently wrong, and roughly how much each one is worth. The free check runs 3 times a day per visitor and keeps every run from the first one, so a site you check today can be compared with the same site in a month. There is no login and no card. An account exists for people who want the same 60 tests run for them on a schedule and kept in one dashboard. #### Where do these rules come from? The SEO rows follow documented behaviour rather than folklore: title and description handling, canonicals, robots directives, sitemaps and mobile-first indexing are all described by Google in public. The speed row uses Google's own PageSpeed Insights, which is the same Lighthouse engine that reports Core Web Vitals, so the number you see here is the number Google's tool reports. The structured-data rows validate against schema.org types, and the AI-crawler rows check the user agents each vendor publishes for their own bots. Where a rule is genuinely contested, such as how much llms.txt matters today, the row carries a smaller weight and says plainly what it is testing, instead of pretending the industry has settled it. - Google Search Central, the documentation for how the crawler and index behave. - PageSpeed Insights and Lighthouse, for the mobile performance score. - Schema.org, for the structured-data vocabulary. ### Free AEO checker: are you the answer? #### How do I become the answer instead of a result? Give the engine one paragraph it can lift without editing. The strongest pattern is a direct answer of about 40 to 60 words immediately under the H1, written as a complete sentence that would make sense read aloud with no screen. Our 11 AEO tests check for that paragraph first, then for the scaffolding around it. Then phrase your headings as the questions people actually type. A heading that reads "Pricing" is a label; a heading that reads "How much does it cost?" is a question an assistant can match to a query and answer from the text underneath. This single row carries a weight of 10, the heaviest on the AEO side, because it changes more outcomes than anything else we measure. Finally, put facts where a machine can take them whole. Prices, steps, hours and comparisons belong in a list or a small table rather than buried in a sentence. We also check readability, aiming near grade 8, and whether your business name and phone number are consistent between the visible text and your structured data. - A 40 to 60 word direct answer under the H1. - At least three headings phrased as real questions. - FAQ structured data that matches the visible questions. - Prices, steps and comparisons in lists or tables. #### How is a score actually calculated? Every test carries a published weight. A pass earns the whole weight, a warning earns half, a failure earns nothing, and the score is what you earned divided by what was available, rounded to a whole number out of 100. There are 60 tests in a full report. Nothing is averaged from a black box, so the same page checked twice gets the same number twice. A test that cannot run does not quietly cost you points. If the speed provider is unreachable, that row is marked not-available and its weight leaves the denominator entirely, so a provider outage cannot make your site look worse than it is. Rows that need live rank data or a paid API are marked coming, and they are excluded the same way rather than sitting at zero. Weights are not equal because the fixes are not equal. A missing title tag is worth 8 and takes two minutes. Question headings are worth 10 on the AEO side because they are the single strongest signal that a page was written to be quoted. Minifying CSS is worth 1, because in 2026 it almost never changes an outcome on its own. | Score | The question it answers | Tests | Heaviest single test | |---|---|---|---| | SEO | Can Google find, read and rank this page? | 38 | Mobile speed (weight 6) | | AEO | Will an assistant read this page out as the answer? | 11 | Question headings (weight 10) | | GEO | Will an AI answer cite this page by name? | 11 | Structured data depth (weight 10) | #### What should I fix first? Work down by weight, not down the page. The report sorts the worst rows to the top for exactly this reason: three fixes worth 10 each move a score more than fifteen fixes worth 1. Most sites we check have between 4 and 8 failing rows, and two or three of them account for most of the lost points. Read the evidence line before you change anything. Each failing row prints what we actually saw, such as the byte count of the HTML, the exact headings we found, or the crawler that returned a 403. If the evidence does not match your page, you are looking at a cached copy or a different URL, and the fix is to check the address rather than to edit the site. - Fix the heaviest failing row first: the report already puts it at the top. - Re-check after each change. Every check is kept, so the two runs sit side by side. - Ignore any row marked coming: it is excluded from the score, not counted against you. - Treat warnings as half-marks, because that is exactly what they are worth. #### What are the limits of this check? This is one fetch of one page, not a crawl of a site. It reads the HTML the server returns, the response headers, the robots file, the sitemap and the structured data, and it asks a speed provider for the mobile performance of that same address. It does not log in, it does not run your checkout, and it does not see pages that are not linked from the one you gave us. The score is an estimate against a published rule set, not a prediction of where you will rank. Ranking depends on competitors, links and history that no single-page check can see. What this is good for is the opposite direction: it tells you, with evidence, which of the things under your control are currently wrong, and roughly how much each one is worth. The free check runs 3 times a day per visitor and keeps every run from the first one, so a site you check today can be compared with the same site in a month. There is no login and no card. An account exists for people who want the same 60 tests run for them on a schedule and kept in one dashboard. #### Where do these rules come from? The SEO rows follow documented behaviour rather than folklore: title and description handling, canonicals, robots directives, sitemaps and mobile-first indexing are all described by Google in public. The speed row uses Google's own PageSpeed Insights, which is the same Lighthouse engine that reports Core Web Vitals, so the number you see here is the number Google's tool reports. The structured-data rows validate against schema.org types, and the AI-crawler rows check the user agents each vendor publishes for their own bots. Where a rule is genuinely contested, such as how much llms.txt matters today, the row carries a smaller weight and says plainly what it is testing, instead of pretending the industry has settled it. - Google Search Central, the documentation for how the crawler and index behave. - PageSpeed Insights and Lighthouse, for the mobile performance score. - Schema.org, for the structured-data vocabulary. ### Free GEO readiness checker: can AI cite you? #### Why is my site never cited by AI answers? Usually because the crawler never got in. Every AI vendor publishes named user agents, and a robots.txt written years ago for search engines often blocks them by accident, or a firewall returns 403 to anything it does not recognise. We test 14 of them by name, including GPTBot, ClaudeBot, PerplexityBot, Google-Extended and CCBot, and a single blocked crawler is worth more lost points than any formatting problem. The second reason is that there is nothing quotable on the page. An AI answer cites a sentence it can use on its own, which in practice means a paragraph of roughly 40 to 120 words that contains a concrete fact or number and makes sense with no surrounding context. We count how many of those you have, and 5 is the bar for a pass. The third is identity. If nothing on the page states who publishes it in a machine-readable way, an AI has no entity to attribute the claim to. That is what the structured-data row measures: at least 3 rich schema types and sameAs links pointing at the profiles that confirm you are who you say you are. All 11 GEO rows come back to those three ideas: let them in, give them something to quote, and tell them who you are. - Let the 14 named AI crawlers through robots.txt and your firewall. - Publish llms.txt and llms-full.txt at the root. - Write at least 5 self-contained paragraphs that each carry a fact. - Declare Organization, your services and FAQ schema, with sameAs links. #### How is a score actually calculated? Every test carries a published weight. A pass earns the whole weight, a warning earns half, a failure earns nothing, and the score is what you earned divided by what was available, rounded to a whole number out of 100. There are 60 tests in a full report. Nothing is averaged from a black box, so the same page checked twice gets the same number twice. A test that cannot run does not quietly cost you points. If the speed provider is unreachable, that row is marked not-available and its weight leaves the denominator entirely, so a provider outage cannot make your site look worse than it is. Rows that need live rank data or a paid API are marked coming, and they are excluded the same way rather than sitting at zero. Weights are not equal because the fixes are not equal. A missing title tag is worth 8 and takes two minutes. Question headings are worth 10 on the AEO side because they are the single strongest signal that a page was written to be quoted. Minifying CSS is worth 1, because in 2026 it almost never changes an outcome on its own. | Score | The question it answers | Tests | Heaviest single test | |---|---|---|---| | SEO | Can Google find, read and rank this page? | 38 | Mobile speed (weight 6) | | AEO | Will an assistant read this page out as the answer? | 11 | Question headings (weight 10) | | GEO | Will an AI answer cite this page by name? | 11 | Structured data depth (weight 10) | #### What should I fix first? Work down by weight, not down the page. The report sorts the worst rows to the top for exactly this reason: three fixes worth 10 each move a score more than fifteen fixes worth 1. Most sites we check have between 4 and 8 failing rows, and two or three of them account for most of the lost points. Read the evidence line before you change anything. Each failing row prints what we actually saw, such as the byte count of the HTML, the exact headings we found, or the crawler that returned a 403. If the evidence does not match your page, you are looking at a cached copy or a different URL, and the fix is to check the address rather than to edit the site. - Fix the heaviest failing row first: the report already puts it at the top. - Re-check after each change. Every check is kept, so the two runs sit side by side. - Ignore any row marked coming: it is excluded from the score, not counted against you. - Treat warnings as half-marks, because that is exactly what they are worth. #### What are the limits of this check? This is one fetch of one page, not a crawl of a site. It reads the HTML the server returns, the response headers, the robots file, the sitemap and the structured data, and it asks a speed provider for the mobile performance of that same address. It does not log in, it does not run your checkout, and it does not see pages that are not linked from the one you gave us. The score is an estimate against a published rule set, not a prediction of where you will rank. Ranking depends on competitors, links and history that no single-page check can see. What this is good for is the opposite direction: it tells you, with evidence, which of the things under your control are currently wrong, and roughly how much each one is worth. The free check runs 3 times a day per visitor and keeps every run from the first one, so a site you check today can be compared with the same site in a month. There is no login and no card. An account exists for people who want the same 60 tests run for them on a schedule and kept in one dashboard. #### Where do these rules come from? The SEO rows follow documented behaviour rather than folklore: title and description handling, canonicals, robots directives, sitemaps and mobile-first indexing are all described by Google in public. The speed row uses Google's own PageSpeed Insights, which is the same Lighthouse engine that reports Core Web Vitals, so the number you see here is the number Google's tool reports. The structured-data rows validate against schema.org types, and the AI-crawler rows check the user agents each vendor publishes for their own bots. Where a rule is genuinely contested, such as how much llms.txt matters today, the row carries a smaller weight and says plainly what it is testing, instead of pretending the industry has settled it. - Google Search Central, the documentation for how the crawler and index behave. - PageSpeed Insights and Lighthouse, for the mobile performance score. - Schema.org, for the structured-data vocabulary. ## Questions and answers **Is this really free?** Yes. Three checks a day per visitor, no login and no card. Creating an account adds tracking over time and a fix plan. **What do SEO, AEO and GEO mean?** SEO is being found in Google’s blue links. AEO is being the direct answer: featured snippets, People-also-ask and voice assistants. GEO is being named and cited inside AI answers from ChatGPT, Google AI Overviews, Perplexity and Gemini. **How is the score calculated?** Each test has a published weight. A pass earns the weight, a warning half, a failure none. Rows that need live rank or AI data are marked “coming” and are not counted. **Do I need to sign up?** No. Enter the address and read the report. Sign up only if you want us to keep watching the site. **Which tests are run?** Title and description, H1 and H2, image alt text, link ratio, viewport, canonical, noindex, www redirects, OpenGraph, schema, sitemap, robots.txt, freshness, broken links, page size, response time, caching, minification, PageSpeed mobile score, theme and plugin exposure, directory listing and HTTPS. **Why does my score differ from other tools?** Every tool weighs tests differently. Ours publishes its weights, and the same page always gets the same score here, so you can measure change over time. **What is AEO?** Answer Engine Optimization: shaping a page so Google’s featured snippets, People-also-ask boxes and voice assistants use it as the answer. **What does the checker look for?** A 40–60 word direct answer under the H1, headings phrased as questions, FAQ and HowTo schema, readability around grade 8, lists and tables, consistent business name and phone, and a visible updated date. **What is GEO?** Generative Engine Optimization: being read, trusted and cited by AI answer engines. It starts with letting their crawlers in and giving them a guide (llms.txt). **Which AI crawlers are checked?** GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-Web, anthropic-ai, PerplexityBot, Google-Extended, Googlebot, Bingbot, Applebot-Extended, CCBot, Bytespider and Meta-ExternalAgent. **Do you generate llms.txt and JSON-LD?** The fix text tells you exactly what to publish; generated files land in the fix plan for account holders. ## Facts and limits - One fetch of one page, not a crawl of a site. It does not log in and does not see unlinked pages. - The score is an estimate against a published rule set, not a prediction of ranking position. - Every check is kept from the first one, so the same address can be compared over time. - Crawler user agent: PageRankNinjazBot/1.0. It obeys robots.txt. - Free tier: 3 checks per visitor per day, no account.