Reads the source page
Submit a URL or paste raw HTML. The app fetches or accepts the page source, cleans noisy markup, and prepares it for analysis.
Review a page, detect existing JSON-LD, understand the main entity, and generate a practical schema implementation blueprint.
Schema Analyzer is built for teams that need a repeatable way to audit webpages for structured data opportunities without manually reading every line of HTML.
Default links assume the app uses the current /schema-analyzer base path. Update the CTA href values if your deployment path is different.
Raw HTML-first schema audit tool
Review saved schema audits and open detailed JSON or table views.
Schema Analyzer helps SEO, content, development, and structured data teams inspect a webpage from its raw HTML, understand what the page is really about, and produce a clean schema plan that can be reviewed, refined, and implemented.
Submit a URL or paste raw HTML. The app fetches or accepts the page source, cleans noisy markup, and prepares it for analysis.
It identifies page intent, main entity, major sections, visible facts, existing JSON-LD, and recommended schema types.
Users receive a dashboard record, overview, schema stack, property table, warnings, placeholders, and a JSON-LD blueprint.
The app is intentionally simple: choose the page input, select the audit mode, run the analysis, and review the structured result from the saved audit detail screen.
Users sign in before accessing the dashboard, audit form, or admin tools.
Select Conservative, SEO-focused, or SEO + GEO based on how broadly the review should evaluate opportunities.
Provide a webpage URL or paste raw HTML directly when you do not want the app to fetch the page.
Open the completed audit to inspect schema stack, property rows, warnings, placeholders, and generated JSON-LD.
These feature areas come from the current Express routes, EJS views, database tables, and audit service flow.
Run audits against a live URL or paste raw HTML for controlled review, staging pages, private pages, or saved source snapshots.
The audit flow first builds page understanding, then generates the final schema audit using structured JSON output.
The app extracts any existing application/ld+json blocks so users can compare current markup against the recommended blueprint.
Detailed table views show schema type, nesting, parent, property, value, source section, status, and notes.
Audits are stored in SQLite with status, source type, model name, timestamps, creator, project, and final output.
Admins can create users, assign roles, and create project records that organize audit work.
The uploaded project did not include image screenshots, so these previews recreate the actual EJS screens and CSS patterns as editable HTML.
Users start with a minimal login card. The app requires an active user account before dashboard, audit, or admin access.
Session-protected accessRaw HTML-first schema audit tool
The dashboard lists saved audits with project, status, creator, date, and an Open link for the detailed report.
Saved audit historyRaw HTML-first schema audit tool
Review saved schema audits and open detailed JSON or table views.
Users name the audit, optionally assign a project, select a mode, and provide either a URL or raw HTML.
Conservative · SEO-focused · SEO + GEORaw HTML-first schema audit tool
The current app saves status values such as queued, processing, completed, and failed. Users see these as dashboard and detail badges.
processingRaw HTML-first schema audit tool
https://example.com/product-page
The audit detail page combines overview metadata, schema stack, table view, warnings, placeholders, stage-one understanding, existing JSON-LD, cleaned HTML, and final JSON-LD.
completedRaw HTML-first schema audit tool
https://example.com/product-page
| Schema Type | Role | Nested Status | Status | Reason |
|---|---|---|---|---|
| WebPage | Page-level container | top-level | recommended | Represents the audited page. |
| Product | Main entity | nested | recommended | Visible product facts support this entity. |
{
"@context": "https://schema.org",
"@type": "WebPage",
"mainEntity": {
"@type": "Product",
"name": "Example Product"
}
}
Admin users can create user accounts, select roles, create projects, and review existing users and projects from one screen.
admin accessRaw HTML-first schema audit tool
| Name | Client |
|---|---|
| Credit Cards | Example Bank |
| Local SEO | Example Client |
On small screens, admin form and tables stack vertically.
The final report is designed for review and implementation. It separates high-level understanding from schema implementation detail.
Page URL, page type, main entity, main entity type, and confidence level.
Recommended schema types, roles, nesting status, parent relationships, status, and reasoning.
Schema properties mapped to visible values, source sections, statuses, and notes.
Flags missing data, uncertain assumptions, and values that should be confirmed before implementation.
A pretty JSON-LD string saved as the final blueprint for review and implementation planning.
Audit status, cleaned HTML summary, source status, model name, created-by user, project, and timestamps.
Instead of manually scanning raw HTML and existing schema blocks, users start from a structured summary, table view, and JSON-LD plan.
Every audit follows the same flow, modes, output categories, and saved dashboard history.
The tool distinguishes supported facts from placeholders and warnings, helping teams avoid over-modeling or inventing missing values.
Schema stack, property rows, statuses, and notes give SEO and development teams a clearer path from analysis to implementation.
Use the dashboard to review saved audits, or go straight to the new audit form with a URL or pasted HTML.