All in One SEO Pack Integration

Geo Controller provides geographic tag replacement that can be used alongside All in One SEO (AIOSEO) to create location-aware SEO metadata.

Geo Controller uses IP geolocation to provide geographic information such as the visitor’s country, city, region, and currency. Its geographic placeholders, including %%country%%, %%city%%, and %%region%%, can be replaced during WordPress HTML rendering when they are preserved in the generated output.

This provides additional opportunities for geographic metadata personalization. However, dynamic SEO titles and descriptions should be configured carefully, particularly on websites relying on organic search traffic.

How the Integration Works

Geo Controller includes a geographic tag replacement system that processes supported placeholders in the generated WordPress HTML.

When a supported geographic placeholder appears in the final HTML output, Geo Controller can replace it with information associated with the current visitor’s IP address.

For example, %%country%% can become United States for a visitor detected in the United States or United Kingdom for a visitor detected in the United Kingdom.

This integration is different from AIOSEO’s native Smart Tags system. Geo Controller geographic placeholders are not necessarily registered or displayed as selectable AIOSEO Smart Tags.

For geographic replacement to work, AIOSEO must preserve the literal placeholder in its generated HTML metadata. Compatibility may therefore depend on the installed AIOSEO version and the specific editor field.

How to Use Geo Controller with All in One SEO

Install and activate All in One SEO.
Install and activate Geo Controller.
Verify that Geo Controller returns the expected geographic information for your visitors.
Open a WordPress post or page and locate its AIOSEO settings.
Find the SEO Title or Meta Description field.
Enter a Geo Controller placeholder as literal text, such as %%country%%, if the field supports retaining custom text.
Save the page and inspect the generated HTML source to verify whether the placeholder was replaced.

Note: AIOSEO’s Smart Tags editor may process or normalize field content differently from a regular text field. If the placeholder is removed, modified, or interpreted as unsupported content, Geo Controller cannot replace it using its general HTML tag replacement mechanism.

For information about AIOSEO’s native Smart Tags, see Using Smart Tags in Titles and Descriptions.

Available Geographic Tags

Geo Controller provides a collection of geographic placeholders that can be used in supported WordPress output.

Some commonly used examples include:

Geo Controller Tag	Description
`%%country%%`	Detected visitor country name.
`%%country_code%%`	Two-letter country code.
`%%city%%`	Detected city name.
`%%region%%`	Detected region or state.
`%%continent%%`	Detected continent name.
`%%currency%%`	Currency code associated with the detected location.

The actual values depend on the geographic information available for the current request.

For additional properties and examples, visit the Geo Controller Tags documentation.

Important: The list of Geo Controller tags is separate from AIOSEO’s native Smart Tags. The availability of a geographic property does not guarantee that every AIOSEO metadata field will preserve or render its placeholder.

Using Geographic Tags in SEO Metadata

Geo Controller placeholders can be combined with ordinary text to construct location-aware titles and descriptions, provided the placeholders survive AIOSEO’s metadata processing.

Example: Geographic SEO Title

Suppose you operate a business providing services in multiple countries.

You might configure a title containing the following geographic placeholder:

Our Services in %%country%% | Example Company

If the placeholder is preserved and Geo Controller detects Germany, the resulting HTML title may be:

Our Services in Germany | Example Company

Example: Geographic Meta Description

You could also use a geographic placeholder in a meta description:

Explore our products and services available in %%country%%. Contact our team to learn more.

When the detected country is Serbia, the generated description may become:

Explore our products and services available in Serbia. Contact our team to learn more.

These examples demonstrate geographic text replacement. They do not guarantee that search engines will index or display every geographic variation.

All in One SEO Settings Example

The screenshot below illustrates the historical use of Geo Controller placeholders within All in One SEO settings.

Note: This screenshot shows an older AIOSEO interface. Modern AIOSEO versions use a different metadata editor and Smart Tags system, so the configuration process and compatibility may differ.

How to Verify Geographic Metadata

Do not rely exclusively on the SEO preview displayed inside the WordPress administration area.

To verify the generated metadata:

Save the post or page containing your geographic placeholder.
Open the public page in a browser.
Use View Page Source to inspect the server-generated HTML.
Locate the page’s <title> element or <meta name="description"> tag.
Check whether the geographic placeholder was replaced with the expected value.
Repeat the test using different visitor locations where possible.

If the placeholder remains unchanged in the final HTML, verify that AIOSEO preserved the original text and that Geo Controller’s tag replacement system processed the response.

If the placeholder does not appear in the HTML at all, AIOSEO may have removed or transformed it before Geo Controller could perform the replacement.

Important SEO Considerations

Geographically personalized metadata is not a substitute for a complete international SEO strategy.

Search engines may crawl your website using IP addresses from locations different from those of your intended customers.

For example, a search engine crawler connecting from the United States may receive metadata intended for visitors from that country, even if your website produces different metadata for European visitors.

As a result, using geographic tags does not guarantee improved rankings, regional indexing, or location-specific search results.

Google Search and International SEO

Google recommends dedicated regional or language-specific URLs with appropriate hreflang annotations when websites provide different regional or language versions of their content.

IP-based metadata personalization alone does not replace these practices.

For additional guidance, read Google’s documentation on locale-adaptive pages.

Avoid Misleading Metadata

Geographic metadata should accurately describe the products, services, or information available on the page.

For example, generating a title about services in a particular country is inappropriate if those services are not actually available there.

Avoid producing misleading regional claims or substantially different search-facing descriptions that do not match the page content.

Page Caching and Dynamic Metadata

Geo Controller’s general geographic tag replacement occurs during WordPress HTML generation.

If a caching plugin, reverse proxy, or CDN stores the resulting HTML, subsequent visitors may receive metadata generated for a different geographic location.

For example, a page cached with a title containing Germany may continue displaying that title to visitors from other countries until the cache is refreshed or separated by geographic location.

Client-side JavaScript cannot be relied upon to correct server-generated SEO metadata for search engine crawlers.

Review page caching and CDN configuration before using geographic placeholders in metadata on production websites.

All in One SEO can generate metadata used by social media platforms, including Open Graph information.

However, social media platforms typically retrieve page metadata through automated crawlers rather than through the browser of the person sharing a link.

Therefore, any geographic personalization may reflect the crawler’s detected location instead of the person sharing or viewing the content.

Social media services may also cache titles, descriptions, and images independently.

For predictable social media previews, stable metadata is generally preferable to visitor-dependent geographic descriptions.

Privacy and Sensitive Information

Not every geographic or technical value should be included in publicly accessible SEO metadata.

Avoid exposing individual visitor IP addresses, precise coordinates, network identifiers, or other potentially sensitive information in titles, descriptions, and social metadata.

Broad geographic information, such as a country or region, is generally more appropriate for public content personalization.

Recommended Best Practices

Use geographic placeholders only where they accurately describe the page content.
Verify that your AIOSEO version preserves custom placeholders in the generated HTML.
Prefer stable SEO titles and descriptions for important organic search landing pages.
Use dedicated regional URLs and hreflang where appropriate.
Inspect the actual HTML source rather than relying only on the SEO editor preview.
Review caching and CDN behavior before enabling visitor-specific metadata.
Test how social media crawlers retrieve and cache your page information.
Avoid inserting sensitive visitor information into public metadata.
Do not assume that geographic personalization will improve search rankings.

For Developers

Geo Controller provides a general HTML tag replacement mechanism for supported geographic properties.

In the publicly available implementation, the CFGP_Public::output_buffer_callback() method processes placeholders using the geographic data supplied by Geo Controller.

Developers can customize the data passed to the general tag replacement mechanism through the cfgp/render/tags WordPress filter.

This mechanism is separate from AIOSEO’s native Smart Tags registration system.

For advanced integrations, developers should inspect the currently installed versions of Geo Controller and AIOSEO and use their supported APIs where appropriate.

For more information, see the Geo Controller PHP Integration documentation and AIOSEO Developer Documentation.

Important: Geo Controller’s geographic placeholders are an optional customization mechanism. Their use inside AIOSEO metadata depends on the installed version and whether the placeholders are preserved in the generated HTML. Incorrect geographic targeting, misleading metadata, or inadequate caching configuration may negatively affect search visibility. SEO improvements are not guaranteed.