Status codes tutorial: review and fix

HTTP Code: The numeric response a server sends when a page is requested. Code 200 indicates success. 3xx codes are redirections, 4xx are client errors (like the famous 404), and 5xx are server errors.

Internal Navigation: Links within a page that point to other pages on the same domain. They are fundamental for search engines to discover and crawl all site content.

If this check fails, review the technical report to see:

• The returned HTTP code (should be 200)
• The number of internal links detected
• The number of unique destinations
• The result of each sub-check separately

If the HTTP code is not 200, that is the priority problem. If the code is correct but there are few unique destinations, the problem is navigation architecture.

• 404 Error: The page does not exist. Restore the content or create a 301 redirect to the most relevant URL.
• 500 Error: Server error. Review Apache/Nginx error logs, verify PHP configuration, and review application code.
• 403 Error: Forbidden access. Review file and directory permissions and .htaccess configuration.
• 301/302 Code: The page redirects. Ensure the final URL responds with 200.

• Implement a main navigation menu with links to key site sections.
• Add breadcrumbs to facilitate hierarchical navigation.
• Include contextual links within content ("Read more about...", "See also...").
• Add a footer with links to legal, contact, and main section pages.
• Avoid using JavaScript to generate navigation links if possible.

After applying changes, re-run the AISEO audit for this URL. The check should show:

• HTTP Code: 200
• At least 4 unique internal destinations
• Both sub-checks as PASS

You can also use browser developer tools (Network tab) to manually verify the HTTP code.