- Home
- Skills
- Marketing & SEO
- WordPress to Webflow Migration QA: Check Before Launch
WordPress to Webflow Migration QA: Check Before Launch
Compare your WordPress site with Webflow staging, review missing pages and content changes, and check redirect destinations after launch.
$1
Works with the AI Agents you already use
WordPress to Webflow Migration QA: Check Before Launch
Example session with this skill installed
Compare the public Travel Global WordPress and Webflow research websites: https://juthesis2024.wordpress.com/ and https://juthesis2024.webflow.io/. Review the suggested destination-page match, then compare the verified page pair.
- Read your context and instructions
- Compiled the wordpress to webflow
Public website test result
This run used two publicly accessible Travel Global research websites built independently in WordPress and Webflow. They share a subject and content, but are not a production customer migration.
| Check | Result |
|---|---|
| WordPress pages captured | 3 |
| Webflow pages captured | 2 |
| Capture failures | 0 |
| Initial same-path comparisons | 1 homepage pair |
| Changed-path candidate | /destinations/ → /travel-destinations |
| Compared pairs after supplying the verified mapping | 2 |
What the report found
The homepage title, description, H1, extracted text, and image counts differed. The destination pages differed in title, description, H1, text, image alt coverage, and canonical URL. These are review items, not proof that either independently built website is defective. The old WordPress hello-world post remained unmatched.
Checks on the corrected behavior
The WordPress sitemap contained image locations, which were excluded from page discovery. Webflow had no sitemap, so its destination page was found through an internal link. The generated HTML and JSON reports included the page evidence and coverage.
Six separate local regression checks also passed: nested sitemap discovery, discovery through internal links, filtering image locations, detection of a one-digit phone-number change, capture of delayed text and images, and fetching otherwise undiscoverable pages supplied in a confirmed mapping. Forms, CMS behavior, rankings, and the Agensi live runtime were not tested.
Connects securely to your tools. The creator never sees your data.
About this skill
Move from WordPress to Webflow with a clearer launch checklist. Compare the old site and the new staging site, review page-by-page differences, and check confirmed redirects after launch.
What you get
- An HTML report with page coverage, fetch failures, screenshots, and side-by-side evidence for detected changes.
- A JSON report and CSV mapping: same-path matches are provisional, and changed-path suggestions require your confirmation.
- Checks for differences in page titles, descriptions, headings, extracted text, images, internal links, canonical URLs, and noindex settings.
- A saved old-site snapshot for follow-up comparisons and a separate post-launch redirect check.
How it works
- Provide your old site and publicly accessible Webflow staging URLs. The tool reads robots.txt and common sitemaps, then follows same-site page links within the page limit.
- Review the report and confirm suggested URL pairs in the CSV. Re-run the audit with your confirmed mappings.
- After your redirects are configured and the new site is live, check the confirmed mappings against the live domain.
Built for
Webflow freelancers, agencies, and site owners reviewing a WordPress migration. It examines publicly accessible pages; no WordPress or Webflow account connection is required.
Requirements and limits
Requires Node.js 18+, playwright-core, a Chromium-compatible browser, terminal access, network access, and permission to write the report locally. Without a sitemap, the tool follows same-site page links from the supplied URL within the page limit. Blocked or failed pages are reported as unverified. The tool does not migrate the site, publish changes, configure redirects, submit forms, verify CMS or plugin behavior, or guarantee search rankings. Screenshot and content differences require human review. The URL mapping CSV is for review, not direct Webflow import.
Requires Node.js 18+ and Playwright. Cannot audit forms, interactive elements, or backend CMS data. Does not automatically upload redirects to Webflow.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Requires