URL inventory
Every public page and useful file
We record URLs, search traffic, content, forms and redirects before rebuilding anything. You get a faster website with a checked path from every valuable old page.
Changed URLs, missing pages, broken forms and lost metadata often appear after launch. We make those items part of the migration plan before design or development begins.
We record one decision for every important old URL: keep it, improve it, merge it or redirect it. We also record titles, language links, structured data, forms and post-launch checks in the ledger.
Every public page and useful file
Landing pages, clicks and indexed URLs
Text, media, metadata and language versions
Forms, search, calculators and downloads
A named destination for every changed URL
Status, canonical, hreflang, forms and analytics
Choose this when editors rely on the CMS, its permissions and its business modules. We update, simplify and test it without changing the public URL structure unnecessarily.
Choose this when the site mainly publishes stable pages, catalogues or articles. Astro can reduce runtime maintenance while forms and other live functions remain connected services.
Record the public site, important search pages and current behaviour.
Confirm content, functions, languages and editorial work that must survive.
Create representative pages first, then compare the new output with the record.
Test redirects, forms, analytics, robots rules and rollback before DNS changes.
Check crawling, errors, enquiries and priority pages after release.
01A complete old-to-new URL record
02Redirect rules and exception list
03Checked titles, canonicals and language links
04Form and enquiry delivery tests
05Search Console and analytics launch checks
06A rollback and observation plan
No responsible migration can promise fixed rankings. We reduce avoidable losses by preserving useful URLs and content, testing redirects and monitoring the live release.
No. We can update the current CMS, rebuild on Astro or keep the CMS as a private content source. We choose the route after checking how your team operates.
Yes, but the migration ledger remains separate from visual decisions. This makes missing content and broken functions easier to spot.
Yes. We record language relationships, localized URLs, canonicals and hreflang tags, then test them in every published language.
We will inspect the public footprint and tell you what must be protected, what can be removed and which migration route fits.