A phone-repair site built on WordPress goes live after a redesign. Its screen-repair page opens normally, but Search Console reports that the page is not indexed. Before changing the copy or installing another plugin, check what the site is telling search engines.
WordPress SEO settings affect search visibility, URLs and page signals. Some live in WordPress itself; others come from a theme or SEO plugin. None can guarantee a ranking. The useful question is whether the public page sends the signals you intended.
What Counts as a WordPress SEO Setting?
Start with three decisions: may search engines index the site, which URLs represent its pages, and what does each page say about itself? WordPress has sitewide controls for visibility and permalinks. A theme or plugin may add page-level robots instructions, titles, descriptions, canonicals and an XML sitemap. Check the published URL, because a dashboard setting is only useful if it produces the expected output.
This is an implementation check, not the whole of SEO. The page still needs to answer a real search need and have internal links. For the wider process, see technical SEO basics.
Is the Site Asking Search Engines to Stay Away?
In Settings → Reading, WordPress offers “Discourage search engines from indexing this site.” If a public site should appear in search, check that this box is not selected. When selected, WordPress asks search engines not to index the site; it does not password-protect it or stop normal visitors opening pages.
Then inspect the actual page. A theme or plugin can set noindex for one URL even if the sitewide box is clear. Look for a robots meta tag or HTTP header, and inspect the exact URL in Google Search Console. Removing a noindex instruction makes a page eligible for consideration; it does not force Google to index it. The indexing and noindex guide explains that distinction.
Are the Public URLs Stable?
In Settings → General, confirm the public Site Address matches the domain people should visit. The WordPress Address points to where WordPress files live and may legitimately differ when WordPress is installed in a subdirectory. Do not make them identical without understanding that setup.
In Settings → Permalinks, choose a readable structure before publishing many pages. A URL such as /screen-repair/ is easier to recognize than one with an opaque ID. A readable slug is useful for people, but changing the permalink setting is no ranking shortcut. On an established site, changing URLs also means planning redirects from the old addresses and updating internal links. See redirects and status codes.
Which Pages Should Be Indexed?
Not every WordPress URL needs to appear in search. The useful screen-repair page may deserve indexing; a duplicate tag archive or a private account page may not. Make the decision page by page and check the resulting noindex output. Do not apply noindex to an entire content type because one page is thin. Private account information needs login protection; noindex is not a security control.
If two public URLs show much the same content, a canonical tag can indicate the preferred version. It is a preference, not an order to Google, and it is different from noindex. See canonical URLs before changing both controls at once.
Which Sitemap Is the Site Publishing?
WordPress core provides an XML sitemap index at /wp-sitemap.xml. An SEO plugin may replace or disable that output. Find the sitemap URL the live site actually publishes. Check whether it includes the screen-repair page you want discovered and omits URLs that redirect, are noncanonical or deliberately noindexed. A sitemap can be wrong even when it loads successfully.
Submit the sitemap in Search Console if you use one. It helps Google discover preferred URLs, but submitting it does not guarantee crawling or indexing. Our XML sitemap guide shows how to inspect the list.
What Does the Published Page Say?
Open the screen-repair URL and check its HTML or rendered output: is the <title> descriptive, does the page have a clear main heading, is the meta description relevant, and are its robots and canonical tags what you expect? Use your browser’s View Page Source to check HTML tags. A robots instruction can also arrive in an HTTP response header; inspect the response in the browser’s Network panel or with a header-checking tool. A plugin preview is not proof of the live output. Google may show a different title link or snippet for a particular search.
Finally, follow the site navigation to that URL. A sitemap is not a substitute for normal internal links. Fix a missing or broken link before fine-tuning snippet text.
A First Check on One WordPress Page
- Choose the public screen-repair page and record its intended final URL.
- Check Settings → Reading, the intended Site Address and permalink in Settings → General and Permalinks, the page-level robots instruction, and whether the live URL returns a normal response.
- Compare its canonical, sitemap entry and internal links with the URL you intend Google to use.
- Inspect that exact URL in Search Console. Use the reported reason for exclusion or the selected canonical to decide what, if anything, to change.
If Search Console reports no access or index-control problem, the next question is whether the page answers the searches you want it to appear for.
Frequently Asked Questions
How Do I Set SEO in WordPress?
First check Settings → Reading and Permalinks, then inspect a published page for its title, robots instruction, canonical, sitemap entry and internal links. The final URL matters more than a plugin's dashboard score.
Why Isn't My WordPress Website Showing Up on Google?
There is no single cause. Check whether the site discourages indexing, whether the exact page sends noindex, whether Google can access it, and what Search Console reports for that URL. Removing an obstacle does not guarantee indexing.
Which SEO Plugin Is Best for WordPress?
There is no universal best plugin. Choose one that supports the controls you need, and check the live output after configuring it. Avoid assuming that installing or switching plugins will make pages rank.