The homepage is publicly reachable, loads correctly, and works as the intended live entry point.
Homepage accessible
This check verifies whether the homepage is publicly reachable and available as the real entry point of the site. In a WordPress launch or handoff process, the homepage should load correctly for visitors and remain accessible to search engines without avoidable blocking or access restrictions. It is about public availability, not WCAG or interface accessibility compliance.
Why it matters
The homepage is usually the main public entry point of a website. If it is unavailable, blocked, restricted, or behaving inconsistently, both users and crawlers may fail to access the site correctly. That creates a weak launch setup from the start.
This is also important for search visibility. Google recommends making sure the homepage is accessible and not blocked by robots.txt, noindex, or login requirements. If the homepage cannot be reached cleanly, core discovery and indexing signals become less reliable.
What to review
Before marking this check as correct, review the following points:
- The homepage should return a normal public response and load correctly.
- It should not require login, password protection, or private access to be viewed.
- It should not be blocked unintentionally by crawl or index controls.
- The public version should be the real homepage, not a broken placeholder or incomplete holding page.
- Key assets should load well enough for the homepage to function as the visible entry point of the site.
How PreFlight checks this check
PreFlight requests the public homepage and verifies whether it is reachable from the outside as expected. The goal is to detect whether the main entry URL of the site is actually available and usable before delivery.
This check helps surface cases where the homepage is blocked, unavailable, restricted, or technically exposed in a way that does not match a real production-ready site. It is a simple but essential signal in a technical launch checklist.
PASS / WARN / FAIL
The homepage is reachable, but its behavior or public accessibility still needs review before launch.
The homepage is blocked, restricted, broken, or does not function as the real public entry point.
Common mistakes
- Leaving the homepage behind a login or password wall.
- Publishing a site where the homepage still shows a placeholder, maintenance page, or incomplete staging state.
- Blocking the homepage through
robots.txtornoindexby mistake. - Assuming the site is live because internal users can see it, while public visitors cannot.
- Ignoring broken assets or response issues on the homepage before launch.
FAQ
Is this check about web accessibility standards?
No. This page is about whether the homepage is publicly reachable and usable as the site entry point, not about WCAG or interface accessibility compliance.
Can the homepage load for me and still fail this check?
Yes. Internal access, cached sessions, or privileged access can hide problems that affect public visitors or search engine crawlers.
Why is the homepage so important in a launch review?
Because it is usually the first URL users and crawlers see. If the homepage is not accessible, the site is not technically ready for publication.
Check your WordPress site before delivery
Reduce rework, catch last-minute issues and review critical points before launch.
Run analysis