Crawl and vitals · Beginner · an hour
How to wordPress SEO first steps — Indexable First, Then Fast, Then Measured
You have published a site nobody can find, and you need to know whether the problem is a checkbox, the page weight, or simply time.
The short answer
Start with the three settings that decide whether the site can be indexed at all: the Reading visibility checkbox unticked, permalinks set to Post name, and one SEO plugin producing exactly one set of title and canonical tags. Nothing else you do matters until those are right, because a site excluded at the crawl stage cannot be optimised into visibility.
Then treat performance as part of the same job rather than a separate project. Core Web Vitals are read from real Chrome visits at the 75th percentile — LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1 — and Search Console is where you find out whether your pages clear them.
By the HostingFast team · Reviewed 24 August 2026
Beginner
Depth assumed
5
Checkpoints end to end
Free
Cost of asking us
Proven
Verified where you'll run it
This is groundwork, not tactics. Every step here is a one-off configuration you get right once and never revisit, which makes it the highest-return hour available on a new site.
Two feedback loops close the guide: Search Console for coverage and queries, and field vitals for whether real visitors experienced the speed you measured on your own machine. Lab numbers explain the mechanism; field numbers decide whether it counted.
The three switches that decide whether you exist
Settings, then Reading: 'Discourage search engines from indexing this site' must be unticked. Settings, then Permalinks: Post name, locked in before you publish anything, or you will be writing redirects for URLs that already have links pointing at them. And robots.txt should not be disallowing the paths you want crawled.
Verify rather than assume. `curl -s https://yourdomain/robots.txt` and a look at the page source for a stray noindex take under a minute and rule out the single most common reason a new site sees no impressions at all.
One plugin, one set of tags
Yoast or Rank Math covers titles, meta descriptions, sitemaps and schema. Pick one and commit. Running both produces two title tags, two canonicals and two sitemaps, and search engines resolve that ambiguity in whatever way suits them rather than you.
Check the output rather than the settings screen: view source on a post and confirm there is exactly one title, one canonical and one description. Themes ship their own SEO features too, and a theme quietly emitting a second canonical is a genuinely common fault.
Vitals are not a separate project
Field data is real Chrome traffic at the 75th percentile, which is where the Core Web Vitals thresholds are assessed: LCP at or under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1. A lab score of 97 taken on your own fibre connection proves the mechanism improved; only the field figure proves visitors felt it.
For most WordPress sites the largest contentful paint is a hero image, so the levers are its dimensions and format rather than a plugin. WebP conversion is built in here at no extra cost, and server-level LiteSpeed caching keeps cached HTML well under 200 ms, which is where the first-byte budget is won.
Search Console as the only honest feedback loop
Verify ownership with a TXT record or the plugin's snippet, submit the sitemap, and you have the one dashboard where Google tells you directly how it reads your site: which URLs are indexed, which were excluded and why, and which queries you actually appear for.
Then write for one query per page. A page with a single search intent, a deliberately chosen title and a description matching it will outperform four pages hedging across the same ground — and Search Console is where you notice when two of your own pages are competing for the same term.
Where the vitals start from a good place
Every runbook here was exercised on the platform we actually operate — cPanel, LiteSpeed, NVMe storage, one-click installs — so the numbers quoted come from the same stack your site will run on.
NVMe storage and LiteSpeed caching power every tier, from the smallest plan up — speed is the baseline here, not an upsell.
- LiteSpeed caching built into the server, not patched in by plugin
- Built-in WebP image optimisation at no extra cost
- NVMe SSD storage on every tier, not just the expensive ones
- Human support on duty every hour of every day
Why HostingFast
Standard on every plan
Crawlability before cleverness
Three settings decide whether anything else matters, and they are checked with curl rather than trusted.
Output verified, not settings
You confirm one title, one canonical and one sitemap in the page source — where duplicate SEO plugins actually show up.
Real thresholds, named
LCP under 2.5 s, INP under 200 ms, CLS under 0.1, read at the 75th percentile of real visits.
Field over lab
A change that moves a lab score and never moves the field figure improved a benchmark, not an experience.
The server half already handled
LiteSpeed caching and built-in WebP mean the first-byte and image levers are largely pulled before you start.
Scoped honestly
The groundwork is a beginner-level job — about an hour, and almost none of it needs doing twice.
Quick Start
From order to online
- 1
Prove the site is crawlable
Untick 'Discourage search engines' under Settings, then Reading. Then `curl -s https://yourdomain/robots.txt` and check a page source for a stray noindex. This is the reason most new sites see zero impressions.
- 2
Lock the permalink structure before publishing
Settings, then Permalinks, then Post name. Change it later and every existing URL needs a redirect, so this is a decision worth making on day one rather than month three.
- 3
Run exactly one SEO plugin, then read the source
Yoast or Rank Math, not both. Then view source on a post and confirm one title tag, one canonical, one description. Themes emit their own tags too, and duplicates hide there.
- 4
Wire up Search Console and submit the sitemap
Verify with a TXT record or the plugin snippet. Coverage reports and query data are the only direct feedback Google gives you about how your site is being read.
- 5
Read the field vitals, then fix the biggest one
PageSpeed Insights field data at the 75th percentile: LCP under 2.5 seconds, INP under 200 ms, CLS under 0.1. On WordPress the usual culprit is the hero image's pixel count, not a plugin.
Built In
Loaded onto every plan
- LiteSpeed caching built into the server rather than patched in by plugin
- Built-in WebP image optimisation at no extra cost
- NVMe SSD storage on every tier, not just the expensive ones
- Free SSL on every plan, renewed automatically before it can expire
- Per-site PHP version switching from the control panel
- Staging environments for testing changes before they ship
- WordPress and 400+ other applications installed in one click
- Daily backups, with self-service restores you run from the panel
- Human support on duty every hour of every day
- A renewal price identical to the price you signed up at
Frequently Asked
What people ask us most often
How do I tell whether a new site is being crawled at all?
Search Console's coverage report, and it will name the reason if it is not: excluded by noindex, blocked by robots.txt, discovered but not indexed. Before that data arrives, `curl -s https://yourdomain/robots.txt` and a look for a noindex tag in the page source answer the same question in under a minute.
Do Core Web Vitals belong in an SEO checklist or a performance one?
Both, and separating them wastes effort. They are assessed on real Chrome visits at the 75th percentile — LCP under 2.5 seconds, INP under 200 ms, CLS under 0.1 — and they appear in Search Console alongside your coverage data. On WordPress the fix is usually the hero image's dimensions and format, which is an SEO task and a performance task at once.
Can I bring in a domain I already own?
Yes, and it is routine. Unlock the name at your current registrar, take the auth code, and start the transfer from your client area. Remaining registration time carries across, and DNS keeps resolving throughout, so nothing goes dark while the transfer runs.
Does hosting include mailboxes on my own domain?
Yes — every plan includes mailboxes on your domain, with webmail, IMAP, POP and SMTP plus spam filtering on from the start. There is also standalone email hosting for a domain whose website lives somewhere else entirely.
Keep reading
How to Create an Email Forwarder
Route an address to wherever the person answering it actually reads mail, and understand what that does to the delivery path — beginner, about 3 minutes each.
How to Create a Professional Email Signature
A signature that renders in every client without dragging a 400 KB image behind it — beginner, roughly 30 minutes.
Best Drupal vs WordPress
Weighed on the numbers that differ: build model, plugin ecosystem, and what each does to page weight.
Magento Hosting
Plans with the memory ceiling and PHP headroom Magento genuinely needs.
OpenCart Hosting
One-click OpenCart on storefront-tuned PHP, with free SSL and staging included.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Start with the server half already fast.
LiteSpeed caching, NVMe storage and built-in WebP on every tier, plus free SSL and engineers on shift at any hour.
View Magento Hosting plans