## Preparing to review migrated content in the website interface
Before you start checking results, make sure the migration task has already finished in the Migration Tool. If you have just completed the previous step, use [Running Homepage Migration Tasks](doc:running-homepage-migration-tasks) as your reference for the task run itself, then return here for the review work. Do not begin checking the website while the migration is still in progress, because you may see partial content, missing sections, or menu items that have not finished updating yet.

Use an account that can access the admin area, such as an Administrator or Content Editor account. After signing in, open the website area you want to review. If your Sherkety ERP & Website Platform setup includes more than one website or language version, confirm you are looking at the correct site before you compare any results. This is especially important when the homepage, menus, or page titles differ between language versions.

Focus your review on the parts of the website that were included in the migration scope. In most homepage migrations, that means checking:

- The homepage itself
- The top navigation menu
- Footer links
- Key landing pages linked from the homepage
- Shared buttons and calls to action

It helps to decide in advance how you will review each page:

- **Published view** to see exactly what visitors see
- **Edit mode** to inspect sections, content blocks, and editable areas
- **Both views** when you want to compare appearance with editability

In Sherkety ERP & Website Platform, the main areas you will use are the homepage, the website navigation, the page list, and the page editing screen. Keep these open as you work so you can move quickly between visible content and editable content.

[SCREENSHOT: homepage open in published view with top menu and Edit option visible]

## Checking what changed on the homepage after migration
1. Open the homepage from the website menu and review it from top to bottom before making any edits. Compare the visible banner, main heading, supporting text, buttons, images, and section order with the result you expected from the migration. Pay close attention to the first screen visitors see, because this area usually contains the most important message and primary action buttons.

2. Continue down the page and check each homepage section in sequence. Look for cover sections, text areas, image blocks, trust content, service highlights, comparison areas, team content, FAQ areas, and any call-to-action sections that should appear on the homepage. Confirm that each section appears once, in the correct position, and that no section is missing or repeated.

3. Click **Edit** and inspect the same homepage again in edit mode. Select several migrated sections one by one to make sure they can still be clicked normally. If a section is difficult to select, overlaps another section, or causes the layout to shift unexpectedly, note it as a migration issue for follow-up.

4. Test the main homepage buttons and linked items. Open the primary call-to-action buttons, service links, and menu entries that appear in the hero area or major homepage sections. Confirm they lead to the intended internal page and not to an outdated destination, blank page, or missing page.

When reviewing the homepage, common warning signs include:

- A heading with missing text
- Buttons with no visible label
- Images that do not load
- Extra spacing between sections
- A section appearing twice
- A button opening the wrong page

[SCREENSHOT: homepage in edit mode with several migrated sections highlighted]

## Reviewing migrated pages, menus, and visible content details
1. Open the page list in the website area and confirm that the expected migrated pages are present. Review the page titles carefully and compare them with the planned migration result. If your team expected a specific set of landing pages, service pages, or informational pages, verify that each one appears in the list.

2. Check the visible page details that matter most during review:
   - **Page title**
   - **URL**
   - **Publication status**

   A page may exist in the list but still be unavailable to visitors if it is not published, so do not stop after confirming the title alone.

3. Review the top navigation menu and footer links. Make sure the labels are correct, the order matches the intended structure, and nested items appear under the right parent item if your menu uses grouped navigation. Then click through several items to confirm each one opens the correct page.

4. Open a sample of migrated pages and inspect the visible content on each page. Check headings, paragraph text, images, embedded media, buttons, and section spacing. If a page includes rich text formatting, make sure lists, bold text, and paragraph breaks still display properly.

Look for these common visible issues during page and menu review:

- Missing page images
- Empty sections with too much white space
- Text formatting that looks broken
- Menu items shown twice
- A page title that does not match the menu label
- A footer link that opens the wrong page

This review is easier if you move between the page list and the live page view rather than checking everything from one screen only.

[SCREENSHOT: page list showing titles, URLs, and publication status]

## Confirming that editable content still works correctly
1. Open a migrated page and click **Edit**. Test several content areas directly on the page. Select text blocks, image areas, and reusable sections to confirm they are still editable. You should be able to click into content, make a small text change, and move between editable sections without the page becoming unstable.

2. Try basic editing actions on a few migrated sections. For example, click a text area to confirm the cursor appears, select an image block to confirm its controls open, and test whether sections can still be selected in the correct order. If a block cannot be selected or appears locked in place unexpectedly, record that as a follow-up issue.

3. Open the page settings or page properties area and verify that core page details can still be managed. Check that the page name, URL, and publish state are still available and editable where expected. A successful migration should not prevent you from managing these page details afterward.

4. If your site uses more than one language, switch to another language version in the website editing interface and confirm the migrated content is still available there as expected. Review translated headings, buttons, and page labels instead of assuming the default language is the only version affected.

5. Make one small, non-destructive test change, such as adding a short word to a text block, then click **Save**. Refresh the page or reopen it to confirm the change remains. After confirming that saving works, remove the test change and save again so the review environment stays clean.

This step is about proving that migrated content is not only visible, but still manageable through the normal editing tools in Sherkety ERP & Website Platform.

[SCREENSHOT: page edit view with text block selected and Save option visible]

## Running practical follow-up checks across the site
1. Start from the homepage and navigate through the site the way a visitor would. Use the main menu, homepage buttons, and footer links to move through the most important paths. This helps you catch issues that are easy to miss when checking pages one by one from the admin side.

2. Test the key visitor journeys that matter most after a homepage migration. Open major landing pages, service pages, company information pages, ERP pages, and contact paths that are linked from the homepage. If the homepage promotes a specific area, make sure that journey still feels complete from first click to destination page.

3. Check internal links and action buttons on the pages you open. A page can look correct while still containing broken navigation. Click buttons that lead to related pages, contact sections, or inquiry steps and confirm they open the expected destination.

4. Review both desktop and mobile layouts for the homepage and a few migrated pages. On smaller screens, look for hidden text, overlapping buttons, cropped images, or sections with awkward spacing. On desktop, check alignment, section width, and whether content appears balanced across the page.

5. Test interactive elements that appear on migrated pages. If a page includes forms, search, expandable content, or other clickable elements, confirm they still open and behave normally. You do not need to submit unnecessary entries during review, but you should confirm that the visible interaction still works.

Useful follow-up checks include:

- Opening the homepage in both light and dark display modes if your team uses them
- Switching language versions and repeating a few key navigation checks
- Comparing visitor view with edit view when something looks inconsistent

[SCREENSHOT: homepage and a linked landing page reviewed on desktop and mobile layouts]

## Fixing common issues found during the review
1. If homepage sections are missing, duplicated, or out of order, reopen the homepage in **Edit** mode and compare the visible section sequence with the expected migrated layout. Select each section carefully and confirm the structure matches what should appear from top to bottom. If the section exists but is misplaced, adjust it in the editor and save your changes.

2. If a menu item opens the wrong page, go to the website menu settings and review that item’s destination. Check both the menu label and the linked page. Correct the destination, save the menu update, and test the same menu item again from the public view to confirm the fix.

3. If an image, banner, or media area does not display, inspect that section in the page editor. Confirm the media is still attached to the section. If it is missing, reselect the correct asset or upload it again, then save and refresh the page to verify it now appears correctly.

4. If a page looks correct in edit mode but not in the visitor view, check its publication status first. A page may be available for editing while still hidden from visitors. After confirming it is published, open the public version again and retest the page from the menu or homepage link.

5. If text formatting looks broken, open the affected text block and review headings, paragraph spacing, and list formatting directly in the editor. Clean up only the affected area rather than rewriting the entire page.

When you fix an issue, always retest from the same place where you first noticed it. For example, if the problem appeared from a homepage button, test that homepage button again after saving the correction.

[SCREENSHOT: menu settings and page editor used to correct a broken link and missing image]

## Overview
This document focuses on the review stage that comes immediately after running a homepage migration in Sherkety ERP & Website Platform. At this point, the goal is not to rerun the migration task or redesign the site. Your job is to confirm that the migrated homepage content, linked pages, and navigation still work properly for both visitors and content editors.

The review process in this guide covers four practical areas:

- Checking the homepage in published view
- Inspecting migrated sections in **Edit** mode
- Reviewing page lists, menu items, and footer links
- Performing follow-up checks across key visitor journeys

You will also verify that migrated content remains editable, that page settings such as title, URL, and publish state still behave normally, and that important links continue to open the correct pages. This is especially useful when the homepage contains service highlights, ERP entry points, contact actions, or multilingual content that visitors rely on to move through the site.

Use this guide when:

- A homepage migration has just finished
- You need to confirm what changed before approving the result
- You want to catch missing sections, broken links, or formatting problems early
- You need to make small corrections directly in the website editor

This guide does not repeat how to launch the migration itself. For that task, return to [Running Homepage Migration Tasks](doc:running-homepage-migration-tasks). Here, the focus is on what you should inspect in the website interface after the migration has completed.

## Prerequisites
Before you begin the review, make sure the following are already in place:

- You can sign in to the admin area of Sherkety ERP & Website Platform
- Your account has access appropriate for an **Administrator** or **Content Editor**
- The homepage migration task has finished successfully
- You know which homepage sections, pages, and navigation items were expected to be migrated
- You can access the website area in the correct language or site version if more than one is available

It is also helpful to have these items ready before you start checking pages:

- A list of expected homepage sections in their correct order
- The names of important landing pages linked from the homepage
- The main top menu and footer links you want to verify
- A short list of high-priority visitor journeys, such as homepage to service page or homepage to contact page

During the review, you will work mainly with these interface areas:

| Area | What you use it for |
|---|---|
| Homepage | Checking visible migrated sections and buttons |
| Edit mode | Testing whether content is still selectable and editable |
| Page list | Confirming pages, titles, URLs, and publish state |
| Website menus | Verifying navigation labels and destinations |

If your team maintains multilingual content, plan to repeat at least a small part of the review in each important language version. After you finish the checks in this guide, continue with [Running Homepage Migration Workflows](doc:running-homepage-migration-workflows) for the next step in the Migration Tool sequence.