## **Overview**

OTTO MetaSync is a feature inside SearchAtlas that synchronises meta titles and descriptions between SearchAtlas and your WordPress site. When configured correctly, it can push changes to plugins like AIOSEO. However, MetaSync operates by making API calls on page load, which can contribute to rate limiting errors and slower page load times if the live connection is not managed carefully.

This article explains what is known about how SearchAtlas handles meta deployment to AIOSEO, what MetaSync's runtime dependency means for your site, and what steps to take if you are experiencing rate limiting or performance issues.

## **How SearchAtlas Deploys Meta Changes to AIOSEO**

When SearchAtlas pushes updated meta titles or descriptions to your WordPress site via MetaSync, those values may appear dynamically through the live API connection rather than being written permanently into your SEO plugin's database. This means:

- Meta values delivered through the active MetaSync connection appear on your site as long as the connection is live, but they may not be stored inside AIOSEO's own database fields.
- If you want meta values to be fully persistent and independent of the SearchAtlas connection, you need to also save them directly inside AIOSEO. To do this, open the AIOSEO settings for each page or post in your WordPress admin panel, enter the desired meta title and description into AIOSEO's own fields, and save the record. This removes the live API dependency for those fields.

**Key point:** Saving meta values inside AIOSEO directly is the recommended approach for high-traffic sites or any site where an external runtime dependency could cause performance or reliability issues.

## **MetaSync Runtime vs. Persistent Storage**

Understanding the difference between these two modes helps prevent unexpected behaviour:

- **Runtime (MetaSync active):** Meta titles and descriptions are delivered via the live SearchAtlas API connection. Changes made in SearchAtlas can propagate quickly, but every page load may involve an external API call, which can introduce latency or trigger rate limiting under high traffic.
- **Persistent storage (AIOSEO direct):** Meta values are saved inside the AIOSEO plugin database on your WordPress server. No external API call is required on page load. Updates need to be made in both SearchAtlas and AIOSEO separately, but your site has no external runtime dependency for those fields.

For high-traffic sites or sites with strict performance requirements, persistent storage is the recommended approach.

## **Rate Limiting Errors and Page Load Slowdowns**

If your site is experiencing rate limiting errors or page load slowdowns that appear related to MetaSync, the core issue is that the active MetaSync connection is generating API calls that exceed rate limits or add latency. The known resolution for this is to reduce or eliminate the runtime dependency by saving meta values directly inside AIOSEO rather than relying on the live SearchAtlas connection for delivery on each page load.

To address this:

1. Identify which pages are affected — check whether the slowdowns or errors correlate with pages whose meta values are being delivered via MetaSync rather than stored in AIOSEO directly.
2. For each affected page, open the AIOSEO settings in your WordPress admin panel, manually enter the correct meta title and description into AIOSEO's own fields, and save. Once the values are stored in AIOSEO directly, those pages no longer depend on a live API call for their meta data.
3. If you are unsure whether MetaSync is contributing to the issue or need the MetaSync connection adjusted or disabled at the account level, contact the support team so they can review your specific configuration and take action on the backend if needed. When reaching out, have your site URL, a description of the symptoms (including any error messages and approximate timestamps), and your SearchAtlas account email ready.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.