How to preserve URLs, service pages, metadata, redirects, structured data, and measurement when a site changes.
Planned
Planned as a practical migration guide before it becomes its own route.
Resources for service-business websites
A single hub for repair-versus-rebuild guidance, migration checklists, and performance explanations. Thin top-level topic hubs now point back here until they have enough substance to stand alone.
Content architecture
Plain-language guidance for deciding whether a slow plugin-heavy site should be repaired or rebuilt.
Planned
Guides will prioritize changes an owner can evaluate without jargon.
Forms, phone links, analytics, Search Console, redirects, responsive behavior, accessibility, performance, and whether search engines can correctly find the new site.
Planned
Held in the resources hub until the checklist becomes a complete guide.
Questions before a repair or rebuild
The grade should make the next decision clearer: keep the current site, repair the weak parts, rebuild with preservation, rebuild cleanly, or create a focused landing page.
Will I lose my Google rankings?
No one should guarantee rankings. I inventory important pages, metadata, internal links, Search Console context, and redirect needs before a rebuild changes URLs or structure.
Can you improve my existing website instead of rebuilding it?
Yes. If the content, structure, or customer path is worth keeping, a focused performance, accessibility, form, or mobile repair may be the better recommendation.
Do I have to leave WordPress?
Not automatically. The grade looks at what is slowing the site down, how the business uses the site, and whether repair can solve the problem without a platform move.
What happens to my existing pages and URLs?
Important pages are inventoried. URLs are preserved where appropriate, redirected when they must change, and checked after launch.
What happens to my domain and business email?
Domain and email configuration are handled carefully because they affect real operations. A site launch should not interrupt how customers reach the business.
Can my staff update the website?
That is decided during scope. Some sites need a simple editing path; others are safer with managed updates and a care plan.
Who owns the finished website?
The project scope should state what the business owns, how the site is deployed, and what support continues after launch.
Do you migrate forms and tracking?
Forms, phone links, analytics, conversion tracking, and Search Console setup are part of the launch verification when they are in scope.
Do you write the content?
I can structure and edit website copy, but business-critical facts are reviewed by the client. I do not invent claims, results, service areas, or credentials.
Do you provide hosting and maintenance?
Website care can include hosting support, form monitoring, content updates, technical fixes, and performance checks when purchased.
How long does a typical project take?
A focused repair, landing page, and full rebuild do not take the same path. The grade is used to define the work before a schedule is promised.
How much does a typical project cost?
Pricing is not published until it is finalized. Scope is shaped by page count, content migration, integrations, SEO migration complexity, copywriting, photography, landing pages, and ongoing support.
Use the grade before choosing a service.
The right next step may be repair, rebuild, landing-page work, or care.
Free Website Grade