Internal link weight distribution: menus, footers, and contextual links
Menus, footers, breadcrumbs, and contextual links serve different navigation roles. Map where important pages are linked and fix weak or inconsistent paths.
Read note →Technical implementation for agencies and site owners
I trace crawl, indexation, migration, rendering, Cloudflare, and conversion-tracking failures into the code or configuration that owns them, implement the correction, and verify the live result.
For defined technical failures with a named owner, a safe change boundary, and a production check.
Inspect the evidence
These are real screens from owned systems and public tools. They demonstrate operational depth; they do not imply traffic, ranking, or revenue outcomes.
Four implementation lanes
Each lane stays narrow enough to identify the owning layer, make a safe correction, and verify production.
Measurement
Trace the chain from user action through dataLayer, GTM, GA4, Google Ads, and the reporting state.
Paid-case proof
These records state the implementation boundary and technical verification. They do not claim rankings, traffic, or revenue lift.
Further inspection
Use the browser tools and public notes to prepare evidence before a paid handoff.
Published notes
New notes are linked here immediately and remain available through the complete notes index and Atom feed.
Menus, footers, breadcrumbs, and contextual links serve different navigation roles. Map where important pages are linked and fix weak or inconsistent paths.
Read note →Google no longer uses rel=next/prev. Paginated content needs unique URLs, self-referencing canonicals, and crawlable links through the sequence.
Read note →Find pages present in your CMS, sitemap, analytics, or search data but absent from the rendered internal-link graph, then decide whether to integrate, redirect, noindex, or remove them.
Read note →