BSFNamrata

Hello @evildoer ,

Thank you for your update and for trying the suggested steps.

Based on your description, this does not seem to be the expected behavior. SureRank should retain the SEO metadata you save, and cache purges should not cause the metadata to revert to the default WordPress values.

To help us investigate further, could you please open a support ticket by emailing us at [email protected]

This will allow our team to take a closer look and determine the root cause.

We appreciate your patience and look forward to helping you resolve this.

Kind regards,
Namrata

Hello @dashmahn ,

Thank you for taking the time to report this issue and for providing such detailed information.

I checked the source of the homepage and a few posts. The title tag appears to be outputting correctly without any trailing dash. Please refer to the Screenshot.

Could you please confirm whether you’re still seeing the issue on your end?

If so, would you mind sharing the URL of a page where the title is being displayed incorrectly?

That information should help us better understand where the title may be getting modified and assist with further troubleshooting.

Please let us know what you find, and we’ll do our best to help further.

Best Regards,
Namrata

Hello @eusebiuoprinoiu ,

Thank you for reporting this issue and for providing the detailed analysis.

We investigated the behavior and were able to confirm that it is related to the meta field in the SureMails email log table being stored as a JSON column. On some MySQL 8.0+ setups, certain database export/import methods can result in this error.

As a workaround, you can export the database using an explicit character set, for example:

mysqldump --default-character-set=utf8mb4 your_database > backup.sql

This helps prevent binary character set encoding from being included in the dump and allows the import to complete successfully.

Please give this a try and let us know how it goes.

Thank you again for bringing this to our attention.

Best Regards,
Namrata

Hello @kashif61 ,

Thank you for reaching out!

A 403 error during the Google Search Console connection process is usually related to one of the following:

1. Search Console permissions
Please make sure the Google account you are using has either Owner or Full User access to the property. You can verify this under Settings → Users and permissions in Google Search Console.

2. Google Workspace restrictions
If you are using a Google Workspace account, your organization may be restricting third-party app connections. In that case, you may need to contact your Workspace administrator to allow the connection, or alternatively, try using a personal Google account that has access to the same property.

3. Property URL mismatch
Google treats https://aquilbiz.com and https://www.aquilbiz.com as separate properties, so please ensure the property URL in Search Console exactly matches the Site Address configured in WordPress. You can confirm this under Settings → General in your WordPress dashboard.

4. Security plugin or firewall restrictions
If the account connects successfully but the plugin still returns a 403 error, it is possible that a security plugin, firewall, or server configuration is blocking outgoing requests to Google. You could try temporarily disabling security-related plugins or contacting your hosting provider to help rule this out.

Please let me know the results after checking the above steps, and I will be happy to assist you further.

Best Regards,
Namrata

Hello @manu24max ,

Thank you for sharing such detailed insights.

Could you please open a support ticket by emailing us at [email protected]?

This will allow us to thoroughly review the issue, make necessary changes, and provide you with a development ZIP for further review.

We look forward to assisting you further.

Best regards,
Namrata

Hi @ric11212,

Thank you for your update and for trying the suggested steps.

This behavior is not expected, as each language should retain its own meta settings when using Polylang. To better understand what’s causing this on your site, we’ll need to take a closer look.

Could you please open a support ticket by emailing [email protected] and include your site URL? If possible, you can also attach a screenshot or short screencast that shows the issue.

Our team will review this in detail and assist you further.

We appreciate your patience and look forward to helping you resolve this.

Best Regards,
Namrata

Hi @ric11212 ,

Apologies for the delayed response, and thank you for your patience.

SureRank does support Polylang, and it is possible to manage your homepage meta title and description per language.

If you want to set dynamic meta title and description:

If you set the latest post as your home page, you can set the homepage title and description using dynamic variables such as @sitename or @tagline under SureRank → General → Homepage Settings. These settings are applied globally and will reflect across all languages automatically.

If you want different meta content for each language:

Polylang creates a separate page for each language, and SureRank stores SEO data per page. This allows you to set unique meta for each language individually.

Please follow these steps:

1. Open the translated homepage for each language in the WordPress editor
2. Scroll to the SureRank SEO panel
3. Enter the Meta Title and Meta Description for that language
4. Save the page

Each language will then display its own meta title and description.

You can also set a custom canonical URL for each language by editing the respective page and entering the correct canonical URL in the SureRank settings.

Please refer to the screencast attached for a visual walkthrough of the steps above. If anything remains unclear or you are still seeing the same meta across languages, please let us know. We will be happy to assist further.

Best Regards,
Namrata