An on-page SEO checker reviews the HTML and visible signals of a webpage to identify common technical and content-level issues that can affect how a page is understood, crawled, displayed, and maintained. The PKCapra On-Page SEO Checker analyzes a public webpage URL and brings important on-page signals together in one diagnostic report, including the title, meta description, canonical, robots directives, headings, visible content, links, images, structured data, social metadata, and mobile-related markup.
On-Page SEO Checker
Audit a public webpage for important on-page SEO signals including title, description, headings, canonical, indexability, links, images, language, structured data and page structure.
- URL
- —
- Title
- —
- Meta description
- —
- Canonical
- —
- Robots
- —
- Language
- —
- Charset
- —
The score is a PKCapra diagnostic heuristic based on source-level checks. It is not a Google ranking score and does not predict search performance.
What Does the On-Page SEO Checker Check?
The tool fetches the supplied public webpage and analyzes the HTML available in the response. It then organizes the findings into an overall diagnostic score, grade, priority findings, and a detailed inventory.
The current checker reviews signals including:
- HTTP status
- HTTPS usage
- Page title and title length
- Meta description and meta description length
- Canonical URL
- Robots directives and
noindex - H1, H2, and H3-H6 headings
- Visible word count
- Mobile viewport
- HTML language attribute
- Internal links
- External links
- Empty anchor text
- Images
- Missing or empty image
altattributes - Image width and height attributes
- Responsive image signals such as
srcsetanddata-srcset - Lazy-loading signals
- JSON-LD structured data
- Open Graph metadata
- X/Twitter Card metadata
This makes the tool useful as a first-pass on-page diagnostic rather than a replacement for a complete technical SEO audit.
Why On-Page SEO Matters
A webpage can have strong content and still contain technical or structural signals that deserve attention.
For example, a page may have:
- A missing or unsuitable title
- A missing meta description
- Multiple H1 elements
- No canonical declaration
- A
noindexdirective that prevents indexing - Missing mobile viewport information
- Images without useful alternative text
- Weak internal linking
- Missing social metadata
- Structured data that is absent when it would be useful
- Very little visible text compared with the page’s purpose
These issues do not all have the same SEO significance. Some are direct technical concerns, while others are diagnostic signals that should be reviewed in context.
Google’s documentation describes structured data as a way to help Google understand page content and notes that search appearance can depend on many different systems and signals rather than a single on-page checklist. See the official Google Search documentation.
How to Use the On-Page SEO Checker
Enter the full public URL of the webpage you want to inspect.
For example:
Then select Check Page.
The checker retrieves the webpage and analyzes the HTML response. When processing is complete, the report presents the main signals and findings.
A practical workflow is:
- Enter the public webpage URL.
- Run the analysis.
- Review the overall score and grade.
- Start with the priority findings.
- Inspect title, meta description, canonical, robots directives, and headings.
- Review visible content and link structure.
- Check image accessibility and responsive-image signals.
- Review structured-data and social-metadata signals.
- Fix genuine issues on the website.
- Run the checker again after important changes.
The goal is not to maximize a number blindly. The report should help you identify which parts of the page deserve investigation.
Understanding the Score and Grade
The On-Page SEO Checker provides a diagnostic score out of 100 and assigns a corresponding grade.
The score is a PKCapra diagnostic heuristic. It is not a Google ranking score and does not reproduce Google’s internal ranking systems.
A lower score does not automatically mean that a page cannot rank, while a high score does not guarantee search visibility or rankings.
Use the score as a way to prioritize review rather than as a prediction of search performance.
The individual findings are more important than the number by itself.
Title and Meta Description
The checker examines whether the page contains a title and meta description and reports their lengths.
A useful title should clearly describe the page and help users understand what they will find. A meta description can provide additional context about the page in search results.
The tool uses diagnostic length thresholds to identify titles or descriptions that may deserve review. These are practical checks, not universal ranking requirements.
Search engines may generate or modify search-result titles and snippets based on the page and the user’s query. Therefore, passing a character-length check does not guarantee that the exact title or description will appear in Google Search.
If you need a more focused review of metadata, you can also use the Meta Tags Analyzer.
Canonical URL
The checker looks for a canonical declaration in the page HTML.
Canonicalization helps communicate which URL should represent a set of duplicate or substantially similar URLs. A missing canonical can therefore be worth investigating, particularly on sites where multiple URL variations can expose similar content.
However, the presence of a canonical tag does not by itself prove that the canonical relationship is correct.
Check that the declared canonical:
- Represents the intended version of the page
- Uses the correct URL
- Does not unintentionally point to another page
- Is consistent with the site’s URL strategy
For deeper canonical analysis, use the Canonical URL Checker and the URL Canonicalization Checker.
Robots and Noindex Signals
The checker identifies robots-related directives available in the page HTML and flags noindex when detected.
A noindex directive can be intentional, but if it appears on a page that should be eligible for indexing, it requires immediate investigation.
A useful troubleshooting sequence is:
- Confirm whether the page is supposed to be indexed.
- Check the page-level robots directive.
- Check for an
X-Robots-Tagresponse header when applicable. - Review robots.txt separately.
- Confirm that the page is accessible to search-engine crawlers.
- Check the page in your search-engine webmaster tools after corrections.
For related checks, use the Indexability & Crawlability Analyzer and Robots.txt Analyzer.
Headings and Page Structure
The tool counts H1, H2, and H3-H6 elements so you can quickly inspect the page’s heading structure.
Headings should help organize the content for readers and communicate the hierarchy of the page.
The checker can identify situations such as:
- No H1
- Multiple H1 elements
- Missing lower-level heading structure
- Pages with very limited heading structure
A heading count alone does not determine whether content is well structured. A short page may legitimately need fewer headings than a long guide.
For a more focused heading review, use the SEO Heading Analyzer.
Visible Content
The checker estimates the amount of visible text available in the fetched HTML and reports the visible word count.
Very little visible content can be a useful diagnostic signal, especially when a page is expected to provide substantial information. However, there is no universal word count that every webpage must meet.
A concise page can be appropriate when its purpose is narrow. Conversely, adding unnecessary text simply to increase word count can make a page less useful.
When the checker flags low visible content, first ask whether the page actually satisfies its intended user need.
For content-focused analysis, the SEO Content Score can provide additional signals about content structure, readability, sentence length, headings, links, and keyword usage.
Mobile Viewport
The checker looks for a mobile viewport declaration in the page HTML.
A responsive mobile presentation is important because users access websites across a wide range of devices, and Google also evaluates pages with mobile-first crawling and indexing systems.
The viewport check is therefore a useful implementation signal, but it is not a complete mobile usability or Core Web Vitals test.
For broader mobile-related SEO analysis, use the Mobile SEO & Mobile-First Analyzer.
Language and Character Encoding
The checker reports the HTML language attribute and character encoding information when available.
A correctly declared language can help browsers and assistive technologies understand the document, while an appropriate character encoding helps the browser interpret text correctly.
These signals should be treated as part of overall document quality rather than isolated ranking factors.
Internal and External Links
The checker counts internal and external links and identifies empty anchor text.
Internal links help users navigate related content and can provide useful paths between pages. They can also help search engines discover and understand relationships between pages.
External links can provide useful references and supporting context when they genuinely help the reader.
The checker does not attempt to determine whether every link is strategically appropriate. Review the actual destinations, anchor text, relevance, and context before making changes.
For deeper internal-link analysis, use the Internal Links Crawl Path Analyzer.
You can also review anchor distribution and anchor-text patterns with the Anchor Text Analyzer.
Image SEO Signals
The On-Page SEO Checker reviews images found in the fetched HTML and reports several useful signals, including:
- Total image count
- Images missing
alt - Empty
altattributes - Width and height attributes
srcsetdata-srcset- Lazy-loading signals
Missing alternative text can be an accessibility concern and may also mean that important image context is not communicated effectively in the HTML.
However, not every image should have descriptive alt text. Decorative images can legitimately use an empty alt attribute when implemented appropriately.
The checker also does not download every image to measure its actual binary file size or visually judge image quality.
For a dedicated image-focused audit, use the Image SEO Analyzer and Image Alt Text Checker.
Structured Data
The tool checks for JSON-LD structured data in the page HTML.
Structured data can help search engines understand what a page represents. Google maintains specific documentation for supported structured-data features and their requirements.
However, the presence of JSON-LD does not mean that a page qualifies for a rich result, and the On-Page SEO Checker does not validate every schema property or reproduce Google’s Rich Results Test.
For a deeper structured-data review, use the Schema Markup & Structured Data Analyzer.
Open Graph and X/Twitter Metadata
The checker also looks for Open Graph and X/Twitter Card metadata.
These signals are primarily useful for controlling or improving how URLs can be represented when shared through supported social platforms. They should not be treated as direct substitutes for core search-engine indexing signals.
Missing social metadata can therefore be a useful content-distribution finding even when the page itself is technically indexable.
For dedicated analysis, use the Open Graph Analyzer and X Card Analyzer.
How to Prioritize Findings
Not every warning should receive the same level of attention.
A practical priority order is:
1. Indexing and accessibility issues
Investigate unintended noindex, inaccessible pages, incorrect status responses, or other signals that can prevent a page from being properly processed.
2. Canonical and URL problems
Check canonical declarations and URL relationships when multiple versions of a page may exist.
3. Core page metadata
Review the title and meta description for clarity, relevance, and obvious implementation problems.
4. Content and heading structure
Make sure the page provides useful content and that headings reflect its actual organization.
5. Images and accessibility
Review missing or inappropriate alternative text and image implementation signals.
6. Structured data and social metadata
Validate structured data separately where appropriate and review social metadata according to the platforms you use.
This approach prevents minor warnings from distracting you from more consequential technical problems.
Example: A Page With a Noindex Warning
Suppose the checker reports:
- HTTP status: 200
- HTTPS: Yes
- Title: Present
- Meta description: Present
- Canonical: Present
- H1: 1
- Noindex: Detected
The page may appear technically healthy in several areas, but the noindex finding requires context.
If the page is a private, temporary, or intentionally excluded page, the directive may be deliberate.
If the page is an important landing page that should be indexed, investigate where the noindex directive is being generated and remove or correct it before expecting the page to become eligible for indexing.
Example: A Page With Missing Image Alt Text
Suppose a page contains ten images and several are reported without alt text.
Do not automatically add the same keyword-rich phrase to every image.
Instead:
- Determine whether each image is informative or decorative.
- Add meaningful alternative text where the image communicates useful information.
- Keep decorative images appropriately treated as decorative.
- Avoid stuffing keywords into alt attributes.
- Review the surrounding content and image purpose.
The objective is accurate communication, not simply making the warning disappear.
Example: A Page With No JSON-LD
A missing JSON-LD signal does not automatically mean that the page has an SEO problem.
Structured data is useful for certain content types and search features, but not every page requires the same markup.
If structured data is appropriate for the page, identify the correct schema type and validate the implementation using the relevant structured-data testing tools.
On-Page SEO Audit Workflow
For a new or recently redesigned page, the following workflow can provide a useful first pass:
- Run the On-Page SEO Checker.
- Review the HTTP status and HTTPS state.
- Confirm the intended indexing status.
- Review canonicalization.
- Check title and meta description.
- Review heading hierarchy.
- Check visible content.
- Review internal and external links.
- Inspect image accessibility signals.
- Check responsive image implementation.
- Review JSON-LD.
- Review Open Graph and X/Twitter metadata.
- Fix confirmed issues.
- Re-run the checker.
- Use specialized PKCapra tools for deeper investigation where necessary.
For broader technical analysis, combine the results with the HTTP Status Checker, Broken Link Checker, Indexability & Crawlability Analyzer, and Page Speed Analyzer.
What the On-Page SEO Checker Does Not Do
The tool is intentionally a source-level on-page diagnostic rather than a complete website crawler or search-ranking simulator.
It does not:
- Crawl an entire website
- Execute the target page’s JavaScript
- Reproduce Google’s ranking systems
- Guarantee search rankings
- Guarantee indexing
- Validate every structured-data property
- Perform a full Core Web Vitals assessment
- Download every image and measure its actual binary file size
- Visually evaluate image quality
- Prove that a canonical is the correct canonical
- Determine whether every title or meta description will appear exactly as written in search results
Dynamic content generated only after JavaScript execution may therefore not be visible to the checker.
For JavaScript-related investigation, use the JavaScript Rendering SEO Checker.
Understanding Heuristic Warnings
Some checks in the tool use practical thresholds or pattern-based signals.
For example, a title length outside the tool’s diagnostic range is reported for review. That does not mean that a page automatically loses rankings because its title is one character longer or shorter.
Likewise, the tool’s overall score is not an official search-engine metric.
The correct workflow is to investigate the underlying finding, determine whether it is relevant to the page, and then make an informed change.
Privacy and Processing
The On-Page SEO Checker processes a public webpage URL through the server-side WordPress HTTP request used by the tool.
The checker is designed for publicly accessible webpages and does not require a paid SEO API or an external SEO data subscription.
Because the tool fetches the requested webpage, the target URL must be publicly reachable by the server running the PKCapra plugin. Pages requiring authentication, private network access, or special browser-only access may not be analyzable.
Do not submit URLs containing confidential information in query parameters or other sensitive data that you do not want transmitted to the server performing the analysis.
Frequently Asked Questions
Is the On-Page SEO Checker a Google ranking score?
No. The score is a PKCapra diagnostic heuristic. It does not reproduce Google’s ranking algorithms or provide a prediction of search rankings.
Does a high score guarantee better rankings?
No. Search visibility depends on many factors beyond the signals checked by this tool.
Can the checker crawl my whole website?
No. The current tool analyzes the public webpage URL you submit. It is not a full-site crawler.
Does it execute JavaScript?
No. The analysis is based on the HTML response available to the checker. Content that appears only after client-side JavaScript execution may not be detected.
Does it validate canonical URLs?
The tool detects and reports the canonical declaration found in the HTML, but it does not prove that the declared canonical is the correct canonical for the site.
Does missing alt text always mean an image is wrong?
No. Decorative images may appropriately use an empty alt attribute. The correct treatment depends on the image’s purpose and the surrounding content.
Does every page need JSON-LD?
No. Structured data should be considered according to the type and purpose of the page. The absence of JSON-LD is therefore a diagnostic signal, not automatically an error.
Does the tool measure Core Web Vitals?
No. It reports several source-level page signals but does not provide a complete Core Web Vitals assessment.
Can I use the tool after making SEO changes?
Yes. Re-running the checker after changes can help confirm whether the relevant HTML-level signals have changed.
What should I do if the checker reports many warnings?
Start with the priority findings and issues affecting indexing, accessibility, canonicalization, or important page structure. Then investigate secondary signals using the relevant specialized PKCapra tools.
Related PKCapra Tools
For a broader investigation, combine the On-Page SEO Checker with:
- Meta Tags Analyzer
- SEO Heading Analyzer
- SEO Content Score
- Image SEO Analyzer
- Image Alt Text Checker
- Anchor Text Analyzer
- Internal Links Crawl Path Analyzer
- Indexability & Crawlability Analyzer
- Canonical URL Checker
- Schema Markup & Structured Data Analyzer
- JavaScript Rendering SEO Checker
The most useful on-page audit is not the one with the highest number of warnings cleared. It is the one that identifies genuine problems, distinguishes them from informational signals, and leads to changes that make the page more accessible, understandable, crawlable, and useful to its intended visitors.