Deep audit

Every page. Every link. By hand.

A manual audit of your whole site by the team behind Regensbot, at Ibram & Dawwa in Regensburg. People with real access go through every page, link, template and data source. A written data agreement is signed before anyone logs in.

Request a deep audit

By: The team behind Regensbot, Ibram & Dawwa GmbH, Regensburg
Scope: Every page, every link, every template, every data source you grant
Under: AVV under Art. 28 GDPR and a confidentiality agreement
Price: Quote after a scoping call

Process

Three steps, in this order.

01
Scoping call
We talk through the site and agree what the audit covers. You get a written quote for exactly that scope.
- Templates, markets and languages
- Recent changes, migrations and deadlines
- The access you can grant, and who grants it
02
Written agreement, then access
You sign the agreement before anyone logs in. Then you grant the access it names, from your own accounts.
- Data processing agreement under Art. 28 GDPR (AVV)
- Confidentiality agreement
- Read-only access wherever the tool allows
03
Deep analysis and handover
We go through every page and every link, apply all 138 requirements per template and hand over the report in a walkthrough with your team.
- Every page, link and template
- All 138 requirements, per template
- Report and walkthrough with your team

Scope

What we go through.

The scope inventory. The scoping call settles which parts apply to your site.

The site, page by page

Every page: Crawled from the homepage and the sitemaps, then reviewed by hand, template by template.
Every link: The internal link graph: each link's anchor, target, status and click depth.
Redirects and canonicals: Every redirect and chain, every rel=canonical and the cluster it forms.
hreflang clusters: Each language and country version, its self-reference and its return links.
Orphan pages: Pages in the sitemaps or the logs that no internal link reaches.
Templates and rendering: Every template, raw and rendered, and what changes between the two.
Structured data: The markup on every template, checked against the visible page.

With the access you grant

Search Console: Indexing, URL Inspection and performance, per property.
Server or CDN logs: Verified Googlebot traffic, by status and by template.
Merchant Center: Product data and the problems Merchant Center reports.
CMS or staging: Templates and changes before they ship.
Analytics: To weigh each finding by the pages that carry your traffic.

Against all 138 requirements

Per template: Every requirement applied to every template, MUST and AVOID first.
With evidence: What we observed, on which URLs, and how to reproduce it.
With sources: The knowledge base behind each requirement: 2,228 claims and 128 Google documents.

Security

Signed before anyone logs in.

Before anyone touches anything, we sign a written agreement with you. It has two parts, and it comes before every login, every export and every log file.

AVV

Data processing agreement

Under Art. 28 GDPR. We process your data only on your documented instructions and only for the audit.

NDA

Confidentiality agreement

What we see of your site, your data and your plans stays confidential.

The agreement names

What: Exactly what we access: which properties, accounts, environments and log sources.
How: How the data is stored and who on our side works with it.
When: When access ends and when the data is deleted.

Read-only access wherever the tool allows it.
You grant access from your own accounts, and you can revoke it at any time.
The dates are set in the agreement, for your site.

Deliverable

One report. Every finding sourced.

A prioritized report in the format Regensbot uses: every finding carries its evidence, the fix and the sources it rests on. Then we walk through it with your team, finding by finding.

Prioritized: fails first, MUST and AVOID first
Grouped by template, so one fix reaches every page that shares it
Evidence, fix and sources on every finding
A walkthrough with your team

Demo finding

Demo data

FailDEV-URL-04MUST

Link every indexable page from the normal navigation or a hub page

Template: category · 14 of 1,180 sitemap URLs

Evidence: 14 URLs in the sitemap receive no internal <a href> link, e.g. https://shop.example/de/sale/winter
Fix: Link menus to category pages, category pages to sub-categories and sub-categories to every product or article, all with <a href>. Keep important pages within a few clicks of the homepage. Where not every item can be linked, list the rest in the XML sitemap or a Merchant Center feed as a supplement, not a replacement. Never let a page be reachable only through a canonical tag (DEV-CAN-04).
Test: Crawl from the homepage following only <a href> links and compare the result with the sitemap: sitemap URLs missing from the crawl are orphans. Check the click depth of key templates.
Sources: In-depth guide to how Google Search works
Help Google understand your ecommerce website structure
8 claims · D1-C040 · D2-C005 · D2-C006

Questions

About the deep audit.

01Is the deep audit the software?

No. It is a service by the team behind Regensbot. People with access to your site and data do the work by hand, and the report uses the software's format: every finding with its evidence, fix and sources.

02What access do you need?

Only what you choose to grant, and nothing before the agreement is signed. Search Console, server or CDN logs, Merchant Center, a CMS or staging and analytics each add to what we can check. Read-only wherever the tool allows.

03How is the price set?

After the scoping call, for the scope your site needs: its size, its templates, its markets and the access you grant. You get the quote in writing before anything starts.

04What happens to our data afterwards?

The agreement names when access ends and when the data is deleted. The dates are set there, for your site.

05German or English?

Either. Choose your language in the request.

06Can Regensbot keep checking after the handover?

Yes. Verify the site in Regensbot and connect its sources. Crawls and monitors keep checking the same 138 requirements, and the GitHub Action checks every release, within your plan's limits.