ProRank SEO

Multi-Location Management

Manage multiple business locations with centralised schema and KML output

Pro+ Required. Multi-location management is part of the Local SEO module. Access it from ProRank SEO → Local SEO → Locations Manager tab.

Overview

The Locations Manager supports multiple business locations. Each location is stored independently with its own address, contact details, and status. All active locations contribute to the LocalBusiness schema output and KML sitemap.

Adding Multiple Locations

Click Add Location in the Locations Manager to create each location. Each location form includes:

  • Location Name
  • Phone Number
  • Street Address
  • Email Address
  • City / Website
  • State/Region / Postal Code / Country
  • Status (active / inactive)
  • Set as primary location

Primary Location

One location can be marked as primary using the Set as primary location toggle. The primary location is used as the default in schema output when no specific location context is available.

Schema Output

Each active location generates its own LocalBusiness schema entry. Global settings from the Schema & Settings tab (business type, opening hours, social profiles) apply to all locations. Use the JSON-LD Preview in Schema & Settings to verify the combined output.

KML Sitemap

All active locations with coordinates are included in the KML sitemap at/sitemap-locations.kml. Provide explicit latitude and longitude for each location for accurate map placement.

REST API

Locations are managed via the REST API:

GET /wp-json/prorank-seo/v1/local-seo/locations — list all locations

POST /wp-json/prorank-seo/v1/local-seo/locations — create a location

PUT /wp-json/prorank-seo/v1/local-seo/locations/{id} — update a location

DELETE /wp-json/prorank-seo/v1/local-seo/locations/{id} — delete a location

Best Practices

  • • Fill in all address fields for complete schema output
  • • Provide explicit coordinates for each location for KML accuracy
  • • Set one location as primary
  • • Use consistent address formatting across locations
  • • Set inactive locations to inactive rather than deleting
  • • Verify schema output with Google's Rich Results Test