Pre-reference: 80 technical SEO list of issues and 81-89 feed-in and transfer forms
Mission: Joint confirmation of content technology migration and true request path before release
Objective and readiness
This article combines the page tasks, content information, technical checks and request for quotations since the second phase with the acceptance form for the eightieth technical SEO list of issues and the eighty-first to eighty-nine online and re-testing forms. First, it distinguishes between the first posting of the new website and the re-version of the old website: the former examines the public configuration and the complete path, while the latter also needs to keep records of existing sites, information and traffic and not just the new front page.
Prepares a joint list of fields including page numbers, original addresses, new sites, templates, languages, major tasks, status codes, indexing arrangements, normative objectives, information, forms, responsible persons and results. First, confirm that the page map, title description and inner chain are consistent with the final content, then check the moving end, real HTML and key renderings. The test environment needs access protection, and the protection and indexing instructions should be checked for formal release.
Method of operation
If the old site changes the site, creates a new and old itemized map, prioritizes useful content and access paths, and sets an appropriate permanent re-direction to the corresponding page for the address that needs to be migrated. It is not possible to turn all the old product pages to the front page. Synchronize internal links, canonical, language matching and site maps so that they do not refer to the old address; the unchanged page also checks whether the functionality and content have been modified by the template.
On the basis of a user task test, you will continue to search for information and submit requests, starting with the search for possible details, blogs or PDFs. Record the actual back-office permissions to receive and attach, and check the error feedback.
Apply examples
Assuming that the factory updates its website and maintains most of its product addresses, the team finds that the old blog's inner chain is still on the deleted sample page. It should be judged first, and then the inner chain and migration processing should be updated, and not ignored because the new navigation appears correct. Another form for the foreign language details page still appears in Chinese and should also be repaired as a procurement path defect.
When the new station does not have historical natural search data, you can record the first pages as a starting point for tracking configurations. The old station keeps key pages, queries and queries before re-enactment, and post-dispatch changes. When moving domain names, check the corresponding Search Console settings, and do not run a domain name migration process for all small re-enactments, so that tasks do not match the utility of the tool.
Outputs and acceptances
The output is the completion of the sign-off feed-in receipt form, without impacting, repairing the person responsible, planning and revisiting the results. The receipt and inspection cover the main templates and language and complete the testing of at least one real procurement path; the issue of high-risk open access, receipt of forms and incorrect re-direction should be resolved prior to issuance and cannot be successfully opened on the first page in lieu of a full-station pass.
After completion, the official web site, the date on line, configuration and legacy issues are referred to the ninety-first operational baseline, and the unsolved technical items remain on the technical SEO list of issues.
