Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support BSFNamrata

    (@namratabsf)

    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

    Plugin Support BSFNamrata

    (@namratabsf)

    Hello @ashf ,

    Thank you for your suggestion and for taking the time to share your feedback.

    At the moment, adding custom schema markup via a blank textarea is not supported, as the plugin currently provides schema options through its built-in schema builder only.

    We appreciate your idea and will keep it in mind for future improvements. You can also share your suggestions and stay updated on this request through our official ideas board.

    If you have any further questions or need clarification, please feel free to let us know. We’re happy to help.

    Best Regards,
    Namrata

    Plugin Support BSFNamrata

    (@namratabsf)

    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

    Plugin Support BSFNamrata

    (@namratabsf)

    Hello @devksec ,

    Thank you for reaching out and for sharing the details.

    The behavior you described is related to how the plugin currently handles network activation. When the plugin is network-activated, the required tables are not created for individual subsites, which can affect the logging. Activating the plugin separately on each subsite is the correct approach, and I’m glad to hear that this has already worked for you.

    We understand this is not ideal, especially if it caused missing logs earlier. This has been noted, and improvements to this behavior shall be considered for future enhancements.

    Thank you again for reporting this and for your cooperation.
    Please let us know if you have any other questions. We’re happy to help!

    Best Regards,
    Namrata

    Plugin Support BSFNamrata

    (@namratabsf)

    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

    Plugin Support BSFNamrata

    (@namratabsf)

    Hello @rsioncke ,

    Thanks for getting in touch, and for clearly outlining your questions. I’ll go through each point below:

    1. Removing the category base (/product-category/)
    You can use this filter with SureRank. Please add the following code to your theme’s functions.php file or use a code snippets plugin:

    add_filter( 'surerank_remove_product_category_base', '__return_true' );

    After adding the code, go to Dashboard → Settings → Permalinks and click Save Changes to flush the rewrite rules. This step is necessary for the change to take effect.

    2. Removing parent slugs
    At the moment, making changes to the parent Slug is not supported in SureRank. However, your request has been shared with the development team and noted as a possible enhancement for a future update.

    Please try the resolution provided for category base and let us know how it works for you.

    Thanks again for your patience!

    Best Regards,
    Namrata

    Plugin Support BSFNamrata

    (@namratabsf)

    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

Viewing 7 replies - 1 through 7 (of 7 total)