How we improved AppDesign360’s crawlability and quote page
Our November 2026 release made all 116 pages in the AppDesign360 sitemap reachable through internal links, fixed links to retired URLs, and served the quote page from cache. In three checks after release, the quote page responded in 88–99 ms before the first byte. Here’s what we changed and how we checked it.
The starting point
AppDesign360 is our own agency website. It had three sitemap pages with no incoming internal links and 17 pages with links from only one other page. A shared navigation link sent readers through an old redirect, and Ahrefs recorded 1,037 ms to first byte on the dynamic quote page.
We wanted someone who found a service page in search to be able to understand the offer, find related information, and request a quote, call, or start a chat on a phone.
What we changed
- Links and canonicals. We linked relevant service and technology pages to one another, pointed shared navigation at final URLs, and kept quote variants canonicalized to the main quote page.
- Quote experience. We made the form page cacheable and kept its short-lived submission token on a separate endpoint. Service links preselect the enquiry type so visitors start in the right place.
- Discovery. We submitted the updated sitemap through Search Console and notified IndexNow of the canonical URLs. We tracked Google indexing separately from our own crawl.
What we measured after launch
| Check | Before release | After release |
|---|---|---|
| Sitemap pages with zero incoming internal links | 3 | 0 |
| Sitemap pages with exactly one incoming internal link | 17 | 0 |
| Quote page time to first byte | 1,037 ms in Ahrefs | 88–99 ms across three cached HTTP checks |
The post-release crawl checked all 116 sitemap URLs for a successful HTTP response, matching canonical, one main heading, unique title and description, and readable structured data. Every URL passed those checks.
What to track next
Google’s November 15 Search Console snapshot showed 81 of the 116 submitted pages indexed. After the release, Google accepted recrawl requests for several priority service pages. Later Search Console reports are needed to measure changes in coverage and clicks.
In an isolated test environment, we checked a successful save, a failed save, and declined ad consent. After release, we track confirmed quote submissions, completed calls where tracked, and qualified leads.
Sources and standards referenced
Find the issues limiting your own website
Tell us which services and towns you want customers to find. We can scope a technical audit, improvements to your priority pages, and a plan to measure enquiries.