WordPress has two address fields in its settings. These fields control something important: they are the source for all the machine-readable identity information that gets embedded into every page of your site. When Google or an AI search crawler reads your NaProTechnology page, your endometriosis page, your about page -- each of those pages includes a block of data identifying who you are and where this content officially lives.
If those two fields still contain a staging address from when your site was built, every page on your site is telling Google and AI systems that the authoritative version of your content lives at a server that was never meant to be public. Google follows those instructions. It treats your real domain as secondary.
Why no one catches it
The site works perfectly for everyone who visits it. You can browse every page. Your contact form works. Nothing looks wrong from the outside. The problem only appears in the machine-readable layer of your pages -- the part search engines and AI systems read but human visitors never see.
Without running a technical audit on your site, there's no obvious symptom. Practices can have this misconfiguration running for years. The developer handed over a site that looked great. It does look great. It's just been sending search engines to a dead end every time they try to verify who you are.
What this costs you in AI search
When AI systems like Perplexity or Google AI Overviews are deciding whether to cite your content in an answer, one of the things they check is whether the page's identity information checks out. A page about NaProTechnology that claims to be from one domain but points all of its identity data to a staging server fails that check. The content exists. But the identity is broken, and AI systems are conservative about citing sources they can't verify.
The fix
In WordPress, go to Settings, then General. You'll see two fields: WordPress Address and Site Address. Both should contain your live domain -- the actual address your patients visit. If either one says something like staging.agencyname.com/yoursite or a similar address, that's the problem. Updating both fields to your real domain corrects it immediately. No rebuild, no redesign, no content changes needed. Ask your web developer to verify this if you're not sure how to access WordPress settings.
After the fix, it's worth asking Google to re-read your most important pages -- the NaProTechnology overview, your conditions pages, your about page. The error may have been suppressing those pages in search results for years. Once it's corrected, actively prompting Google to recrawl them speeds up the recovery.
Frequently asked questions
What is the difference between WordPress Address and Site Address?
WordPress Address is where WordPress core files are installed. Site Address is the URL visitors use to reach your site. Both must match your live domain after launch. When a staging subdomain remains in either field, WordPress generates internal links pointing to that staging URL, confusing search engine crawlers.
How does a staging URL end up in Google's index?
If WordPress is generating links and canonical tags pointing to a staging domain, Google follows those signals and may index the staging version instead of your live site. This creates a split-identity problem where your content exists in the index under the wrong address, reducing visibility for NaPro and RRM practice searches.
Is this a common WordPress launch oversight?
It is one of the most frequent technical issues on WordPress sites that started with a staging environment. Many hosting providers set up staging on a subdomain, and the URL fields are not always updated as part of the go-live checklist, leaving practitioners with an invisible identity mismatch.
How do I fix the staging URL problem?
Go to Settings, then General in your WordPress admin. Update both the WordPress Address and Site Address fields to your live domain including https. Save the changes, then verify in Google Search Console that your sitemap and page URLs now reflect the correct domain.
Do I need to redirect the staging domain?
Yes. After correcting the WordPress URL fields, add a 301 redirect from the staging domain to the live domain. This passes any indexing credit that may have accumulated on the staging version and prevents duplicate content from persisting in Google's index.