Intent match
Redirect old product pages to the closest new product or solution page.
Old URL migration and 301 redirect map
A review page for mapping legacy ASBR URLs to the new bilingual information architecture before launch.
| Legacy source | Old URLs should be exported from the current site crawl, server logs, analytics, Search Console and indexed search results. |
|---|---|
| Mapping rule | Map each old page to the closest new page by search intent, product family and business value. |
| Priority URLs | Homepage, About ASBR, Coiled Tubing, Drilling Mud Motor, product categories, high-traffic resources and contact pages. |
| Redirect type | Use server-side 301 redirects for permanent migration and avoid redirect chains. |
| Document note | Do not delete old URLs until redirects, canonical host and sitemap are verified in production. |
Bilingual path
Use English as default international path and Chinese path for domestic search where appropriate.
Audit loop
After launch, monitor 404 hits and add redirects for missed legacy URLs.
Related paths
Related links connect products, solutions, capability evidence, and inquiry paths so customers can move from technical interest to project discussion.
website launch checklist
Review launch checklist.
Products
Open product matrix.
Solutions
Open solution overview.
Customer focus
FAQ content supports search snippets and answers common technical-buyer questions.
Why not redirect everything to the homepage?
Homepage-only redirects waste relevance and can hurt migration quality.
Should every old URL be redirected?
Valuable indexed pages, linked pages and traffic pages should be mapped carefully; low-value noise can go to a helpful 404 or relevant hub.
What should ASBR provide?
Current URL export, old sitemap if available, analytics landing pages, Search Console top pages and any externally linked documents.
Route the inquiry to the right engineering conversation.
Share depth, temperature, obstruction, tool string, or operation goal. ASBR can match the condition to tools, testing support, service scope, and documentation.
Well data, operation goal, tool family, and compatibility notes.
Catalog, datasheet, certificates, capability summary, or case reference.
Engineering consultation, procurement review, partner discussion, or service planning.