Verify the deployed site, not only the folder
A local file can exist while its public URL fails because of path, case or deployment errors. Preserve folder structure and test real URLs after upload. A flattened asset directory can break styling and make a complete page look unfinished.
Check that the root homepage is the intended language and that article URLs resolve to their own content rather than an accidental replacement index file.
Run the baseline checks
- Confirm intended public URLs return the correct page.
- Check internal links, images, stylesheets and scripts.
- Use one clear canonical URL for each page.
- Include intended discoverable pages in the sitemap.
- Review robots and indexing directives for accidental exclusions.
- Verify mobile reading, keyboard navigation and theme contrast.
A sitemap helps discovery but does not replace links from the site. Readers and crawlers should be able to reach the articles through normal navigation.
Static-site checklist
| Area | Test |
|---|---|
| Files | Correct root pages and preserved asset folders. |
| Content | Main answer available without client-side generation. |
| Navigation | Hubs and article links use real destinations. |
| Metadata | Unique title, description and canonical URL. |
| Experience | Readable layouts, useful headings and working controls. |
Worked example: a path problem
Illustrative example: an article references ../assets/ui.css, but deployment places the stylesheet at the repository root. The HTML content may still appear while the layout breaks. The repair is to restore the expected folder path, not redesign the article around the missing stylesheet.
Test both a root page and a nested article. Relative paths can work in one location and fail in another.
Monitor after publication
Use search tools and public-page checks to identify inaccessible URLs or unexpected indexing behavior. Keep a record of structural changes. Do not repeatedly rename stable pages merely to add a keyword variation.
Does a static site need a special AI file?
Ordinary accessible content and discovery fundamentals remain important. Do not treat an optional machine-readable file as a guaranteed route into search results.
Should all files be indexed?
No. The intended reader-facing pages should be clear. Build artifacts, duplicate exports and private material do not need to become public article destinations.
Put this into practice
Test one nested article from its deployed URL through navigation, metadata and assets. Repeat across representative page types before submitting the sitemap.
Primary-source reading for platform details: Google Search Central: technical requirements; Google Search Central: sitemap guidance.
Related foundation: How to choose a performance marketing consultant in Morocco. How these guides are prepared.
Ayoub Mouhachtt
Growth & performance marketing. Explore the portfolio and working background.
Related portfolio work: eGrow. The worked examples in this guide are illustrative and are separate from the portfolio’s project evidence.