Bob Bodily Work with Bob
Menu

Technical delivery

Find and remove the blocks between a bot and your answer.

Test the full request path from DNS and the site edge to final HTML, links, discovery files, and structured data.

Live requests · Repeatable pass tests · No vague health score

Request path

Every layer must return the right result

  1. DNS and TLSDoes the host resolve and connect?
  2. CDN and firewallIs the request allowed and cached correctly?
  3. ApplicationDoes the route return the intended status and content?
  4. HTML and linksCan a basic client find the main answer and next page?
  5. Discovery and schemaDo robots, sitemaps, feeds, canonicals, and facts agree?

Deliverable preview

Representative finding record

Each issue must be tied to a request or a page that someone else can check.

  • URL, request method, user agent, date, and location
  • Status, redirect chain, content type, cache, and firewall result
  • Visible main text and links with JavaScript off
  • Expected result and why it matters
  • Owner, impact, confidence, fix, and pass test

The report also says when no major technical block is found.

Engagement outline

Starting point
A scoped technical review or a custom repair project.
Price
Quoted after route count, stack, edge controls, and access needs are known.
Timing
Set after access is confirmed. A small static site and a large app need different work.
Boundary
Technical access cannot replace weak evidence, poor content, or outside trust.

Scope can include

Checks from the edge to the answer

  • Status, redirects, TLS, canonicals, and content types.
  • Robots rules and verified bot controls at the edge.
  • Main content and links that work without JavaScript.
  • Sitemaps, feeds, schema, and identity data.
  • Cloudflare, CloudFront, origin, cache, and firewall rules.
  • Speed, accessibility, and agent controls.

Public proof you can inspect

This site publishes a crawler access test log, a technical audit checklist, and the exact robots policy. These files show the record format, not a claim that every client needs the same fix.

Good fit

You see crawl, indexing, rendering, edge, sitemap, schema, or performance problems and can provide needed access.

Poor fit

You want technical changes to guarantee rankings, or no one can approve firewall, app, DNS, or deployment work.

Process

How the work runs

  1. Map page types

    Choose representative routes, bots, browsers, and discovery files.

  2. Capture live evidence

    Record requests, responses, page output, rules, and speed data.

  3. Fix by impact

    Repair clear blocks first and keep unrelated changes out of scope.

  4. Prove the result

    Repeat the tests, save the record, and add regression checks where useful.