Replay
Astro site factory: eight trade-business sites, research and checks
A real run, replayed: eight Astro sites for trade businesses, 309 pages in all.
Move your site to or from WordPress, every URL checked.
For owners facing plugin updates or edits that need a developer: same look, same content and URLs. An Astro site became WordPress with 37 of 37 URLs matched and 0 redirects.
- URLs at the same path
- 37 of 37
- redirects needed
- 0
- page text identical, lowest of 36 pages
- 100.00%
- editor blocks, 0 invalid
- 3,418
Title, H1, description and canonical path matched on 37 of 37.
Measured See every URL
Sound familiar
A plugin update threatens your contact form on Friday. Changing a phone number takes a call and an invoice. We move your site either way, keeping your design, content and URLs.
The theme came with the site, and every update keeps you guessing. Moving to static pages removes those plugin updates.
What you get
Your next site keeps the parts you want. Before the move, the plan covers how you edit pages and handle forms.
- Your design and words. We carry over your existing pages and compare their content. You agree on any design changes before rebuilding starts.
- Static pages. For a move out of WordPress, the plan lists which plugins go and how their jobs get done, including contact forms.
- An editable WordPress site. You get a custom theme that controls each page's appearance. You can edit text and photos without calls or tickets.
- Room for new pages. You add service pages, towns and photos through WordPress, with editable content blocks and no page builder or third-party plugin.
- Your URLs and search details. We check page addresses, titles and descriptions. Existing paths stay where possible, and every changed URL gets a permanent redirect [301].
- Files to rebuild from. For a move into WordPress, you receive a comparison of old and new pages, a content export and a rebuild script.
An Astro site moved into WordPress, measured
Parity run: the Astro original against its WordPress build
- 37 of 37 URLs answer at the same path, on WordPress and through the public gate 37 of 37 direct, 37 of 37 gate Measured
- 0 redirects: every page keeps its old address, so no redirect map was needed no-redirect check 37 of 37 Measured
- 37 of 37 title, first H1, description and canonical path identical four checks per URL Measured
- 100.00% page text identical at the lowest; 44,511 words compared average 100.00% Measured
- 37 of 37 structured data graph equal, once the site address and image file names are normalised JSON-LD deep compare Measured
- 3,418 blocks the WordPress editor opened on 36 pages, 0 invalid no Custom HTML blocks Measured
37 of 37 URLs matched for status, title, main heading, description and preferred address path, with 0 redirects. An Astro site, converted to WordPress and parity-checked URL by URL. [H1, canonical path]
The page addresses stayed the same, so the move needed no redirect map.
We direct AI coding agents and check their work. An agent performed this conversion, and scripts checked every URL.
The WordPress build sits behind a gate that keeps the login page, the admin screens and the API away from the public, and its contact form checks every entry.
The conversion walkthrough lists every URL check and what a client receives.
To and from WordPress
We have converted sites into WordPress and out of it.
For your site, we plan either direction around what you need to edit and what you want to keep.
The teardown tool
This part is for the technical reader. Skip to the static build examples to see where a move out of WordPress leads.
Your plugin list comes first: what each plugin does, whether you still need that job done and what would replace it. We look at page content, form handling and editing needs separately before proposing a replacement.
You agree where contact form submissions go. Page titles and descriptions get checked alongside the visible words. The plan also lists changed addresses and the permanent redirects they need.
You review those decisions before the rebuild starts.
An interactive example: runs in your browser
- 01 detect
REST index found: 21 namespaces, 78 routes
Example Heating & Air, theme trade-theme-child (child of trade-theme)
- 02 plugins
seen from outside: 16 (14 via REST, 2 via page source); in the dashboard: 20
- Contact Form 7 dies form endpoint: 1 file, 8 checks
- WPForms Lite dies form endpoint: 1 file, 8 checks
- Elementor dies layout rebuilt as components
- Elementor Proprobable dies layout rebuilt as components
- Yoast SEO dies titles + sitemap written at build
11 more seen from outside
- Smush dies nothing to cache: pages are files
- WP Rocket dies nothing to cache: pages are files
- Wordfence dies no login page on the public site
- Akismet dies honeypot + signed token on the form
- Slider Revolution dies plain HTML; feeds fetched at build
- a Smash Balloon feed pluginprobable dies plain HTML; feeds fetched at build
- Redirection replaced by redirect map in server config
- MonsterInsights replaced by one analytics tag
- Site Kit by Google replaced by one analytics tag
- WP Mail SMTP dies the form endpoint sends the mail
- Complianz keep as a service consent script, scoped in paid teardown
+ 4 more only the dashboard lists (the paid teardown reads it): Really Simple SSL, UpdraftPlus, Classic Editor, Yoast Duplicate Post
- 03 content
34 pages, 112 posts, 860 media files: 146 Markdown files
3 converted below: home.md, furnace-repair.md, contact.md
- 04 urls
196 public URLs keep their exact paths; 3 redirect rules; 3 paths gone (410)
redirects.conf, 159 lines
- 05 after
plugins to babysit after: 0
19 leave, 1 kept as an outside service
A heating and air company’s WordPress site, read by the same code that reads yours.
The static target, checked
These builds went through 12 numbered stages with named checks.
Example
Confluence Water Recovery, Cherry Creek, Denver: Class 4 catastrophic flooding (water damage)
The flooding-service site is one of the eight in the Astro collection.
Example
Ten Mile Heating & Air, Silverthorne: furnace and AC combo replacement (HVAC)
The heating-service site shows another from the same collection.
Example
Prairie Line Radon, Brighton: multi-suction-point radon system for large homes (radon mitigation)
The radon-service site comes from the same collection.
The collection's contact-form handler passed 66 of 66 checks against a test mail server.
These examples show where a move to static pages leads. The measured WordPress conversion above shows the other direction.
One example page, weighed
The home page of the heating and air site, read from its build files: the page itself, one stylesheet, three images and no script files to download.
- 45.1 KB HTML (10.5 KB compressed) Measured
- 40.7 KB 1 stylesheet Measured
- 0 script files to download Measured
- 3 images on the page Measured
The same method on a real move
An old link needs a destination after a move. The tools scanned the original sites, mapped their addresses and generated permanent redirects with a table of expected destinations.
Before release, a comparison checked that the text contained only declared changes. The release process also included a way to undo the release and a check that the site worked. [rollback, health check]
For your move, we compare the old address list with the proposed site before launch. The plan separates paths to keep from changed paths that need redirects.
The migration service explains that process. Move a website lists the available directions.
Start small
Start with a paid teardown to decide which plugins can go. It covers what replaces them and how you edit the new site. You review the plan for leaving WordPress or moving into it before any page moves. You can stop arranging your work around the next plugin update.
Tell us what you would change.
One sentence about the project is enough. Name the tools you already use, or point at an example on this site.