WordPress SEO New York: Fixing the Technical Basics on WordPress Sites

Most WordPress sites I audit for local businesses have no strategy problem at all. They have a settings problem: a box ticked during the build, a sitemap generated twice, a plugin that adds a second set of tags, a contact page with an address Google can’t read as an address. Good WordPress SEO in New York starts by finding and fixing those basics, because nothing you write or build later can work while they are wrong.

I have worked in SEO for more than 16 years, much of it on WordPress, and I work with clients remotely from Bucharest. This article is the checklist I run on a WordPress site for a business that serves customers in New York: indexing settings, permalinks, plugins and sitemaps, speed, and local schema for one or several locations.

For what a full engagement should include, see our article on what belongs in a WordPress SEO services scope. Here I stay with the checks.

Why WordPress SEO New York sites break in the same places

WordPress is flexible, and that flexibility is the risk. A site for a dental practice in Queens or a law office in Midtown is often built by one person, extended by another, and maintained by whoever is available. Nobody owns the whole picture, and the faults are rarely exotic:

• An indexing setting left on from the development phase.
• A permalink structure changed after launch without redirects.
• Two plugins doing the same job, each producing its own sitemap, title or schema.
• A heavy theme or page builder that makes every page slow on a phone.
• One generic contact page for a business with three locations.

None of this is specific to New York. The competition is. When several businesses of the same type sit within a short walk of each other, a technical fault that would cost little in a quiet market can decide whether you are found at all.

Check 1: the indexing switch

Start in Settings, then Reading. WordPress has a box labelled “Discourage search engines from indexing this site”. Developers often tick it while the site is being built, which is sensible, and then forget it at launch, which is not.

The WordPress Reading Settings documentation explains what the box does. Since version 5.3 it adds <meta name='robots' content='noindex,nofollow' /> to the head of every page. It also stops WordPress from pinging update services. The same page notes that “it is up to search engines to honor your request”. Treat a ticked box as a request to every search engine to leave the whole site out.

What to check:

1. In Settings, then Reading, the box is unticked on the live site.
2. View the source of the home page and a few inner pages and search for “noindex”. Only pages you want hidden should carry it.
3. In Search Console, the URL Inspection tool on a key page should report that indexing is allowed.

Check your SEO plugin too. Most can set noindex for whole post types or archives, which is useful for thin archives and harmful when applied to service pages by mistake.

On WordPress, the most expensive SEO mistake is usually one checkbox, not one missing keyword.

Check 2: permalinks, chosen once

Settings, then Permalinks, controls the shape of every URL on the site. The WordPress Permalinks documentation defines permalinks as “the permanent URLs to your individual pages and blog posts, as well as your category and tag archives”, and adds that “The URL to each post should be permanent and never change”.

The options it lists are Plain (?p=123), Day and name, Month and name, Numeric, Post name and Custom. For a local business site, I almost always recommend Post name: short, readable URLs such as /emergency-plumbing/ or /brooklyn-office/. Dates in URLs make sense for a news site, not for service pages that stay current for years.

The important rule is the word “permanent”. If your site launched with dates or IDs in the URLs and has been live for a while, changing the structure changes every URL at once. That can be the right call, but only with a full list of old and new URLs and a 301 redirect for each one, tested before and after the switch. Changing it on a quiet Friday afternoon without redirects is how a site loses traffic it took years to build.

While you are there, look for leftover slugs such as /home-2/ or /services-copy/ from duplicated pages. And if URLs suddenly return 404 errors after a plugin update, the documentation notes that “Visiting the Permalinks screen triggers a flush of rewrite rules”, so opening it is a quick first step.

Check 3: plugins and sitemaps

Plugins are where most WordPress SEO problems hide. I review them in three passes.

First, count and purpose. List every active plugin with one line on what it does. Anything nobody can explain, or that duplicates another, is a candidate for removal (test on a staging copy first). Two active SEO plugins usually means two sets of titles, canonicals or schema.

Second, the SEO plugin’s output. Whichever plugin you use, check what it actually prints on a service page: the title, meta description, canonical, robots tag and structured data. If you use Yoast, our article on what Yoast SEO does and what it can’t do explains where its job ends.

Third, sitemaps. WordPress has its own sitemaps. The announcement of XML sitemaps in WordPress 5.5 says WordPress exposes “a sitemap index at /wp-sitemap.xml“, covering public post types and taxonomies, author archives and the home page. A single sitemap holds “a (filterable) maximum of 2000 entries”, the robots.txt file WordPress generates “will reference the sitemap index”, and when the site visibility setting discourages indexing, “sitemaps will be disabled”. SEO plugins often switch the core sitemap off and provide their own.

What good looks like:

• One sitemap index, submitted in Search Console, and robots.txt pointing to that one.
• Only pages you want in search inside it: no thank-you pages, test pages, attachment pages or empty tag archives.
• Your location and service pages present, with the URLs you actually link to.

Check 4: speed on WordPress

Google’s page on Core Web Vitals and Google search results describes them as metrics that “measure real-world user experience for loading performance, interactivity, and visual stability”, and recommends that site owners achieve good scores. The targets it gives:

The same page says good Core Web Vitals align “with what our core ranking systems seek to reward”. It does not say speed beats relevance, and in my experience it doesn’t: a fast page that doesn’t answer the search won’t rank. But a slow mobile page loses the visitors who did find it.

On WordPress, the fixes follow the causes. Resize and compress images before upload, and serve modern formats. Remove plugins that load scripts on every page for a feature used on one page. Be cautious with page builders that wrap each element in many layers of markup. Use caching, and choose hosting that responds quickly from the eastern United States, where most of your visitors are. Then check the Core Web Vitals report in Search Console, which the page says “shows how your pages perform”.

Check 5: local schema and several locations

Structured data tells Google, in a fixed format, what your page already says in words. For a local business, the type is LocalBusiness (or a more specific subtype). Google’s LocalBusiness structured data guide lists name and address as required, and recommends properties including geo, openingHoursSpecification, telephone and url, described as “The fully-qualified URL of the specific business location.”

That last property matters for businesses with more than one location, for example a Manhattan office and a Brooklyn one, or a clinic group across several boroughs. Google’s guide says to “Define each local business location as a” LocalBusiness type. In WordPress terms, that means:

Three cautions from audits:

• Markup must match the page. The hours and phone number in the schema should be the ones a visitor sees on the page. Plugins that store business details in a separate settings screen often drift out of date.
• No markup for places you don’t have. Adding LocalBusiness markup with an address for every borough you serve, without a real location there, misrepresents the business. Service areas belong on your service pages and your Business Profile, as our guide to local SEO across the five boroughs explains.
• No guarantee. Google says it “does not guarantee that features that consume structured data will show up in search results.” Test the markup with the Rich Results Test, as the guide recommends, and treat it as clarity rather than a ranking lever.

A WordPress SEO check you can run in an afternoon

If you want to know where your site stands before hiring anyone, this is the order I would follow.

Some of these take minutes. Others, such as a permalink change with redirects or a plugin clean-up on a busy site, are worth doing with someone who has done them before. If you would like a structured review rather than a checklist, a WordPress SEO audit covers these points and ranks the fixes by impact. I do this work remotely and bill by the hour, so you pay for the checks and fixes your site needs, not for a package.

FAQ

What do WordPress SEO services in New York usually include?

A sound engagement starts with the technical basics in this article, then moves to content, local profiles and links. Where the provider sits matters less than whether they can show you what they would check and why.

Is WordPress good for SEO for a NYC business?

Yes. Problems come from how a site is configured and extended: settings left on from development, overlapping plugins, heavy themes. Fix those and the platform is rarely the limit.

Do I need a WordPress SEO agency in New York, or can I fix this myself?

Many of the checks above take minutes and need no specialist. Bring in help for changes that can lose traffic if done wrong, such as permalink changes, redirects, plugin clean-ups on a live site or a theme replacement.

Should I use the WordPress core sitemap or my SEO plugin’s sitemap?

Either works. Run one, submit it in Search Console, reference it in robots.txt, and keep only pages you want indexed inside it.