Bulk Audit & SEO Tools
Audit many pages at once and read the results.
On this page
- Running a bulk audit
- Reading results
- Page compare
- Schema generator
- SERP preview
- Web vitals
- Platform tools vs plugin: which to use when
- FAQ
- Do the platform tools require the WordPress plugin?
- How is the bulk audit different from the plugin's site audits?
- Do audits consume credits?
- Can the schema generator output be used on WordPress?
- Related reading
The hydrogenseo.com platform ships a set of standalone SEO tools alongside the WordPress plugin: a bulk audit at /seo/bulk-audit, page compare at /seo/compare, a schema generator at /seo/schema-generator, a SERP preview at /seo/serp-preview, and a web vitals checker at /seo/web-vitals. This page walks through running a bulk audit, reading the results, and knowing when to reach for the platform tools versus the plugin's built-in screens.
You'll need a hydrogenseo.com account; signing up at /signup is free and includes free credits.
Running a bulk audit
The bulk audit is the platform's workhorse: it audits pages in bulk and ranks what's costing you traffic.
- Sign in at hydrogenseo.com and open /seo/bulk-audit.
- Point the audit at the pages you want checked.
- Run the audit and wait for it to work through the pages.
- Read the results: findings are surfaced per page and prioritized, so the top of the list is where the fixes matter most.
The platform's promise is precise: audit every page, rank what's costing traffic, write the fix. Findings aren't just flags; they come with the direction of the fix, and if your site runs the plugin with Hydrogen AI connected, many fixes are one chat message away; see agent recipes.
Reading results
Work the results top-down rather than fixing whatever catches your eye:
- Start with the highest-ranked findings. Prioritization exists so you spend effort where traffic is actually leaking.
- Group by type. Ten pages with missing descriptions are one batch job, not ten tasks. On WordPress, batch jobs are exactly what the agent is for.
- Re-run after fixing. Audits are cheap to repeat; the re-run is your proof the fix landed.
If your site runs the plugin, cross-reference with the plugin's own site audits (duplicate titles/descriptions, keyword cannibalisation, orphan pages, broken internal links, metadata length) and the site health score across its seven areas.
Page compare
At /seo/compare, put pages side by side and compare how they're set up. Two common uses:
- Your page vs your page: why does one guide perform while its sibling doesn't? Compare their setup directly.
- Before vs after: confirm a reworked page is actually configured the way you intended.
Schema generator
At /seo/schema-generator, build valid JSON-LD structured data as a standalone tool: pick a type, fill the fields, get markup. It's useful for non-WordPress sites, one-off pages, or drafting markup you want to review before committing anywhere.
On WordPress sites, prefer the plugin's built-in schema instead: it supports Article, Product, FAQ, HowTo, Recipe, Course, Event, Local Business, Breadcrumbs and more, outputs server-rendered JSON-LD automatically, and its fields support smart tags for dynamic values. See the schema markup overview and schema types reference.
SERP preview
At /seo/serp-preview, see how a title and description render in Google results before you commit to them: lengths, truncation, and overall shape. The plugin has the same superpower inline, with a Google SERP preview that updates as you type in the SEO fields; see SERP preview.
Web vitals
At /seo/web-vitals, check a page's performance signals. Performance is one of the seven areas in the plugin's site health score, and the standalone tool lets you check any URL, including sites where you can't install anything.
Platform tools vs plugin: which to use when
| Situation | Reach for |
|---|---|
| Auditing many pages at once, ranked by impact | Platform bulk audit (/seo/bulk-audit) |
| A site that isn't WordPress, or where you can't install plugins | Platform tools |
| Comparing two pages head-to-head | Platform page compare |
| Day-to-day WordPress editing: titles, meta, schema, previews | Plugin screens, which are live in the editor |
| WordPress-specific findings: orphan pages, broken internal links, duplicates | Plugin site audits |
| Actually fixing findings on WordPress in bulk | Hydrogen AI through the plugin |
| Checking AI/answer-engine readiness | Platform AEO analysis (/seo/aeo-analysis); see AEO |
The short version: the platform measures and compares from the outside and works on any site; the plugin implements and fixes from the inside on WordPress. Together they close the loop: audit on the platform, fix through the plugin, re-audit to confirm.
FAQ
Do the platform tools require the WordPress plugin?
No. Every tool at hydrogenseo.com works standalone on any site. The plugin adds the implementation side on WordPress, plus the agent.
How is the bulk audit different from the plugin's site audits?
The plugin's site audits run inside WordPress with inside knowledge (orphan pages, broken internal links, duplicate metadata across your content). The platform's bulk audit examines pages from the outside, works on any site, and ranks findings by what's costing traffic. They complement each other.
Do audits consume credits?
Platform usage is credit-based via your account. Signup includes free credits, and when credits run out only AI generation pauses. See credits, plans and billing.
Can the schema generator output be used on WordPress?
Yes, but on WordPress the plugin's built-in schema is the better path: it renders server-side automatically and supports dynamic smart-tag values. Use the standalone generator for everything else.