Local SEO Pages Done Right. Finally.

Site Nitro: Locations is the WordPress plugin built to solve the local page management problem that agencies and service businesses have been working around for years — messy page structures, wrong schema, and no scalable way to manage dozens of city pages without losing your mind.

This plugin exists because the problem is real.

After two decades of building websites for service businesses, the local SEO page problem never got easier with existing tools. Every new client with multiple locations or service areas meant the same manual process — creating pages one by one, writing schema by hand, keeping service content consistent across a growing list of cities, and watching the WordPress Pages section turn into an unmanageable flat list with no structure.

The bigger problem was schema. Most sites either skip it entirely or apply it incorrectly — putting address-based schema on service area pages that don’t have an address, or omitting the areaServed markup that tells Google exactly which cities a business serves. These aren’t minor oversights. They’re the difference between a page that ranks and a page that doesn’t.

Site Nitro: Locations was built to solve this problem correctly, once, so it never has to be solved manually again.

A structured local page system for WordPress.

Site Nitro: Locations replaces the standard WordPress Pages section for all local content with a purpose-built post type system. Physical locations and service areas are managed separately — because they are different things with different schema requirements. Services are defined once in a central registry and applied across every location and service area page. Schema is generated automatically, correctly, for every page type.

The result is a local page architecture that is organized, scalable, and built the way Google and AI search systems expect to see it — without requiring a developer every time a new city or service needs to be added.

Locations and Service Areas — Handled Separately

A physical location has an address. A service area does not. This distinction matters enormously for schema markup, and it is where most local SEO implementations get it wrong.

Locations receive full LocalBusiness schema — street address, geographic coordinates, phone, business hours, and service catalog. Service Areas receive areaServed schema — city name, state, and the services offered there — with no address fields, because applying address schema to a city a business serves but does not operate from is technically incorrect and potentially harmful to rankings.

Services Registry

Every service a business offers is defined once in the Services Registry — name, description, call-to-action link, and an optional reference to an existing service page. Services are then selected per location or service area, and the plugin automatically creates child service pages at clean, hierarchical URLs like /locations/missoula/carpet-cleaning/.

One registry. Consistent service content across every city. No rebuilding pages from scratch every time a new location is edited.

Schema Output — Complete and Correct

Every page type outputs accurate JSON-LD schema automatically: LocalBusiness for locations (with address, coordinates, hours, phone, service catalog); areaServed for service area pages (with no address); Service schema for child service pages linked to the parent business; and FAQPage schema generated automatically from FAQ entries on any page.

Schema is output in the page head on every publish. No configuration required beyond filling in the fields.

Content Score

Every location and service area page gets a completeness score from 0 to 100 based on the content signals that matter for local SEO — unique body content, services assigned, schema fields complete, reviews present, FAQs added, featured image set, and SEO meta populated. The score is color-coded: red means attention needed, green means the page is ready to perform.

The score is not decorative. It is a direct indicator of whether a page has what it needs to compete in local search results. The Content Score appears in the post list column view as well — making it easy to see which pages across an entire site need attention at a glance.

Built by an agency owner, not a product team.

Site Nitro: Locations was built by someone who has been managing local SEO for service businesses for nearly two decades. Every feature exists because its absence caused a real, measurable problem on a real client site.

Two post types exist because location and service area schema are fundamentally different. The Services Registry exists because rewriting service descriptions across thirty city pages is the job nobody actually does. The Content Score exists because ‘is this page ready to rank?’ is the question every audit asks and WordPress never answers.

Free gets you started. Pro gets you results.

The free version is a complete, functional local SEO page system — not a crippled demo. Pro unlocks the content richness features that make the difference between pages that rank and pages that sit.

FREE

Free

Available on WordPress.org

PRO

Pro

Starting at $99/year

Straightforward pricing. No surprises.

Solo

$99

per year · 1 site

Business

$249

per year · 5 sites

Agency

$499

per year · 50 sites

14-day money-back guarantee · Annual billing · Cancel anytime

Common Questions

What is the difference between a Location and a Service Area?

A Location is a physical address the business operates from. A Service Area is a city or region the business serves without a physical presence there. The distinction matters for schema — physical locations use address-based LocalBusiness schema, service areas use areaServed schema with no address. Most implementations ignore this difference. Site Nitro: Locations handles it correctly by design.

Will installing this plugin affect my existing pages?

No. The plugin adds new post types alongside your existing WordPress content. Nothing on the current site is touched, moved, or modified. Existing service pages at URLs like /services/carpet-cleaning/ stay exactly as they are. You can optionally reference them from the Services Registry as canonical pages, which strengthens schema without changing any existing URLs.

How does the Services Registry work?

You define each service once — name, description, CTA, and optionally a link to an existing service page. On any location or service area page, you select which services apply. The plugin creates a child service page automatically at the correct URL, pre-populated with the service description. Each child page is independently editable.

Does this work with my existing WordPress theme?

Yes. The plugin uses WordPress’s standard template hierarchy and ships with default templates that inherit your theme’s styles. No page builder is required. If you want full design control, any template can be overridden from your theme folder.

Is this compatible with Yoast SEO and RankMath?

Yes. Site Nitro: Locations outputs its own schema for location and service area pages specifically and coexists with Yoast SEO and RankMath without conflicts. The Content Score panel checks for meta title and description set by your SEO plugin and factors that into the page score.

What happens to my data if I cancel Pro?

All pages, content, URLs, and schema remain fully intact. Your site continues to work exactly as before. You lose access to Pro features for future editing — Reviews Registry, Gallery panel, and other Pro panels become read-only — but nothing is deleted or broken.

Can I use this on client sites?

Yes. The Small Business plan covers 5 sites and the Agency plan covers 50. If you manage more than 50 sites, contact us about volume options.

Does the plugin affect site performance?

No. All pages are real WordPress posts — not dynamically generated. Schema is a lightweight JSON-LD block in the page head. There are no external API calls on page load and no heavy frontend JavaScript.

The local page problem has a solution.

If you manage service business websites and you’ve been building local pages manually — fighting schema, managing dozens of pages with no structure — this is the system that should have existed years ago.