Evidence-led technical SEO

Audits that show their work.

Every finding ships with the exact markup, header, or link that triggered it, plus the rule identifier and the weight it carried in your score. No black box, no vendor folklore.

34 analyzers, one fetch
Metadata, canonicals, indexability, structured data, headings, links, images, accessibility and content depth, all resolved from a single response.
Versioned, arguable scoring
Every point maps to a rule id and a published weight, and each report records the profile that produced it. When a client disputes a number, you can point at the line.
Zero outbound calls
No Google API, no CDN, no telemetry. Fonts, icons, styles and scripts are bundled in the package and served from your own host.

Audit a page

Enter a public URL. The engine fetches it once, analyzes locally, and returns a full report in seconds.

No account needed. Verification runs before the fetch. recaptcha v3 - scored

  1. Resolving host and validating the address range
  2. Parsing the document and indexing the DOM
  3. Running 34 analyzers
  4. Applying scoring profile 2.0
  1. FetchSSRF checked
  2. Parsefault tolerant
  3. Analyze34 rules
  4. Scoreprofile 2.0
  5. Render3 modes
  6. Budget25 s
  • SSRF-hardened fetch
  • Argon2id and rotating sessions
  • CSP, HSTS, frame-ancestors
  • CSRF double-submit

About this application

What AmPuH SEO Intelligence Next does

AmPuH SEO Intelligence Next is a self-hosted technical SEO auditing tool operated by AmPuH Labs. You give it the address of a public web page. It fetches that page once, analyzes the HTML and response headers it gets back, scores the result against published weights, and returns a report that cites the evidence behind every finding.

It is built for site owners, agencies and developers who need to find and fix technical SEO defects on sites they already operate. Running an audit needs no Google account and no sign-in.

  1. You submit one public URL

    No account, no installation on your site, and no tracking code. The page you name is fetched once, over HTTPS, from this server.

  2. The page is analyzed locally

    Analyzers read the returned HTML, response headers and declared structured data: titles, meta, canonicals, indexability, headings, links, images, accessibility and content depth.

  3. Findings are scored and evidenced

    Each finding names the rule that produced it, the weight it carried, and the exact markup, header or link it came from, so a result can be argued with rather than taken on faith.

  4. You read or export the report

    Three modes: an executive summary, a specialist view with the full rule set, and a developer view with raw evidence. Reports can be printed or exported.

Why this application asks for access to a Google account

The audit engine works entirely on its own and makes no Google API calls. Google access is a separate, optional module used by the person who administers this installation, so that reports can include data Google alone holds, and so that the API keys those reports need can be managed in one place instead of being pasted around.

Only the administrator ever sees the consent screen. Visitors running an audit never sign in, and no visitor data is sent to Google. Access is requested in capability tiers, each separately switchable. Only the identity tier is mandatory, and cloud-platform is never requested by default because it is close to full control of a Cloud account.

Scopes requested, and the reason for each
Access requested OAuth scope Why it is requested
Identify the signed-in accountalways openid userinfo.email userinfo.profile Confirms which Google account was connected and shows its email and name in the admin console, so an administrator can see whose grant the installation uses. No contacts, mail, files or calendar data is requested.
Read your Cloud projects default cloudplatformprojects.readonly Lists the projects this account can see so one can be chosen as active. Declined: You must type a project ID by hand and cannot verify it exists.
Create Cloud projects opt in cloudplatformprojects The Create project wizard. Declined: Create the project in Google Cloud Console first, then select it here.
Enable APIs on the active project default service.management The Enable API buttons and the live enablement checklist. Declined: Enable each API manually in the Console; this panel will still report their state.
Manage API keys opt in cloud-platform Create, list, restrict, rotate and delete API keys for PageSpeed and Safe Browsing. Declined: Paste an API key created in the Console. Everything else in the platform still works.
Read Search Console data default webmasters.readonly Property list, and query data for the Search Console tab. Declined: The Search Console tab stays empty.
Read billing status opt in cloud-billing.readonly Shows whether the active project has billing attached. Declined: Billing shows as unknown. Nothing else changes; these APIs have free tiers.

What is never done with that access

  • Google user data is never sold, rented or transferred to anyone, and is never used for advertising or ad profiling.
  • It is used only to produce the reports and administrative screens described above, never for an unrelated purpose.
  • Refresh tokens and client secrets are stored encrypted on this server and are never written to logs, reports or exports.
  • No scope beyond those listed above is requested, and no write access to Search Console data is requested at all.
  • Access can be withdrawn at any time from the admin console, or from your Google Account permissions page, which revokes it immediately.
Privacy Policy Terms of Service About Contact

Manage or revoke this application's access at any time at myaccount.google.com/permissions.

  • PHP 8.2+
  • No database
  • No framework
  • Shared-hosting ready
  • WCAG 2.2 AA
  • PSR-12

Confirm you are human

Drag the handle all the way to the left to release the audit.

Slide to verify
recaptcha v3, scored preparing