What a website check can actually tell you.

Start with the website, then account for the pages.

A homepage can look complete while a service page uses the wrong title or an old internal link returns an error. Website Check starts from your public website and discovers pages through same-site links and available sitemaps. It combines the results into one website report rather than selling separate reports for each page.

The coverage section distinguishes successfully checked HTML, attempted URLs, unavailable responses, excluded URLs, and work that did not finish. A robots restriction is an access boundary. An HTTP 404 is an availability observation. Those should lead to different decisions.

There is no paid page allowance. Operational safeguards still stop unsafe destinations, hostile URL traps, or a scan that cannot finish reliably. An incomplete run does not become eligible for checkout. Review the recorded coverage before deciding whether the finished report is useful.

Fifteen categories, with the affected pages attached.

Recommendations group related observations so the same issue is not presented as dozens of disconnected tasks. Each recommendation identifies affected pages. Expand a category or a page to inspect the underlying observations and limitations. The downloadable JSON retains the full machine-readable record.

A contact link or booking label is a candidate found in source HTML. The check does not submit contact forms, complete bookings, or verify that an email reaches someone. A viewport declaration does not establish that the rendered mobile page is easy to use.

Read a real report structure without treating a sample as proof.

The illustrative five-page report uses fictional saved HTML for a homepage, Services, Contact, About, and Pricing. It is generated from those fixtures without visiting a live customer website.

The sample demonstrates findings and delivery format. It is not a customer result, performance benchmark, ranking improvement, or revenue claim.

Prepare the report first. Choose whether to buy it.

1. Submit a public HTTPS website that you own or are authorized to check.
2. Let the automated job finish public discovery. Review its coverage and free summary.
3. If the completed report is useful, unlock the detailed findings for $5 USD base price plus applicable tax. Stripe shows the final amount before payment.
4. Read the report and save the HTML or JSON download. Follow the access and retention terms shown with your order.

The fee is for the prepared report. Website implementation is a separate service. The $99 Digital IQ Fix begins with an agreed scope; an automated check does not authorize changes to your site or accounts.

A person or an authorized agent can start the same check.

The agent instructions and purpose-built OpenAPI document describe the supported JSON workflow. They explain ownership authorization, scoped access, idempotency, progress, report access, and checkout.

Creating a scan does not charge a payment method. An agent must have permission to request the check and separate permission to proceed with purchase. Supported checkout uses the returned Stripe-hosted payment flow; the API documentation is the authority for the currently available payment methods.

Use the findings as a starting point.

Fix the issue, then verify the affected customer path in the real browser and relevant systems. If you need a manual starting point, use the public website HTML checklist. Search visibility, customer behavior, and business outcomes depend on more than source markup.