FAQ

Confirm the live site isn't still blocked from search engines by a leftover staging noindex tag or a Disallow: / in robots.txt—see common mistakes and the technical SEO checklist. It's the most common and most damaging launch mistake.

Google's three page-experience metrics: LCP (how fast the main content loads), INP (how responsive the page feels to interact with), and CLS (how much the layout unexpectedly shifts while loading). See the performance checklist.

Some tasks (uptime checks, spam moderation) are weekly; others (updates, backup verification) are monthly; deeper reviews (full SEO and security re-checks) are quarterly or annual. See the post-launch maintenance checklist for the full cadence.

Yes, for essentially every site. An XML sitemap helps search engines discover your pages; robots.txt tells them what not to crawl. Both are covered in the technical SEO checklist.

On-page SEO covers content-level choices on each page—titles, headings, meta descriptions (see the SEO checklist). Technical SEO covers whether search engines can crawl and index the site at all—sitemaps, redirects, structured data (see the technical SEO checklist).

Yes. Browsers actively flag non-HTTPS sites as "not secure," it protects visitor data in transit, and it's effectively a baseline requirement rather than an optional extra today. See the security checklist.

That people using screen readers, keyboard-only navigation, or accessibility settings like larger text or higher contrast can genuinely use the site—not just that it looks fine to a sighted mouse user. See the accessibility checklist.

Before. Setting it up after launch permanently loses your launch-period baseline data, which you generally can't recreate later. See analytics & tracking setup.

Yes — see the dedicated e-commerce checklist and local SEO checklist for concerns specific to online stores and location-based businesses.

They're DNS records that let receiving mail servers verify your outgoing email is genuinely from you, rather than spoofed. Without them, contact-form notifications, receipts and password resets are far more likely to land in spam—or be forged by someone else. See the email deliverability checklist.

This site describes general practical groundwork—knowing what data you collect, honest cookie consent, an accurate privacy policy—that's useful regardless of which specific law applies to you. It is not legal advice and can't tell you which regulations actually apply to your business. See the privacy & cookie consent checklist and confirm specifics with a qualified professional.

Losing search rankings and referral traffic because old URLs weren't properly mapped to new ones with 301 redirects. A missed redirect map is the single most common cause of a migration going badly. See the site migration & redesign checklist.

Most of this site's advice applies to WordPress exactly as written. A few things are genuinely platform-specific—plugin hygiene, core/theme update discipline, and WordPress-specific attack vectors like brute-forced logins. See the dedicated WordPress checklist.

For most content-heavy sites, image optimization has the single biggest visible impact—compressing images, sizing them correctly, and lazy-loading what's off-screen. See the image optimization checklist and the broader performance checklist.

No. Privacy, accessibility and consumer-protection requirements vary by jurisdiction and business type. This site covers general best practice; confirm specific legal obligations with a qualified professional. See about this site.