Gulshan Kumar
Forum Replies Created
-
Hello Team Rank Math,
I have followed the suggested steps. Here’s the link to a video showing the complete debugging process from my end.
Steps to Reproduce:
- Use a default WordPress theme.
- Install and activate the free version of Rank Math.
- Enable Advanced Mode.
- Keep the Instant Indexing module enabled from Rank Math → Dashboard.
- Open Rank Math → Instant Indexing.
- Submit any valid URL through the IndexNow API.
Expected Result:
The URL should be submitted successfully.Actual Result:
An error message is displayed in the alert box and the submission does not complete successfully.Thank you.
- This reply was modified 12 hours, 46 minutes ago by Gulshan Kumar. Reason: Clarity
I found the issue. The S3 Location field should contain only the bucket name (e.g.
s3generic://bucket-name) and not the endpoint URL plus bucket path. After changing that and keeping the endpoint in the S3 Endpoint field, Cloudflare R2 worked correctly. The previous configuration produced a misleading SSL handshake error even though the credentials and bucket permissions were valid.This is why placeholder is important. 😄
I have shared it above in the gist URL.
- Please refer to https://gist.github.com/thegulshankumar/f36a1bc4ac938b2d22c23505039350be
- Noted.
Thanks for your assistance.
Forum: Reviews
In reply to: [Forget Spam Comment] Great pluginThank you @qerghgfjkgk for your five-star rating. Your support is appreciated.
Forum: Plugins
In reply to: [Forget Spam Comment] admin-ajax commentsCurrently, the plugin only filters comments submitted through the standard WordPress comment process and does not handle submissions made via
admin-ajax.php.You can find me here for now if you need to reach out or share screenshots during the process.
Hello @guffronmh30,
Thank you for the update. I understand that the Live URL Test is now showing green, which is a good sign.
However, I may be mistaken, but based on additional testing from my side, there still appears to be an issue. When testing your the three URLs you shared, and the sitemap URL using httpstatus.io, the response still shows 404 specifically for Googlebot.
Screenshot: https://i.ibb.co/LDw96LsT/http-status-test-result.png
This usually indicates that the root cause may not yet be fully resolved. Because of this, I would recommend going through the earlier troubleshooting steps again, as it seems the investigation may still be incomplete.
Until the exact reason for Googlebot receiving a 404 response is clearly identified and resolved, issues such as sitemap fetch failures or inconsistent indexing behavior may continue to appear.
Once the underlying cause is addressed and Googlebot consistently receives the correct response from the server, the sitemap should start appearing as successfully fetched in Search Console as well.
Please try completing the remaining troubleshooting steps and let me know the outcome. We can continue investigating from there if needed.
– Gulshan
- This reply was modified 3 months ago by Gulshan Kumar. Reason: Typo fix: except homepage
Hello @guffronmh30,
Thank you for the detailed update and for continuing the investigation. I understand how stressful this situation can be, especially when pages that were performing well suddenly disappear from Google results. You have already taken several good troubleshooting steps.
At the time of testing, I observed that the three URLs you shared return a 404 response specifically for Googlebot, while other crawlers and standard browsers receive a 200 response.
There can be multiple sources that may override this behavior, including the WordPress theme, plugins, theme or plugin functions, an intermediate proxy layer, caching plugin rules, or any custom code snippets configured on the site.
In some environments, security systems such as Cloudflare attempt to verify whether a request is coming from a verified Googlebot. If that verification fails or is misconfigured, the request may be blocked or modified as per settings.
Troubleshooting Steps
To properly isolate the cause, I recommend testing the following steps carefully. After each step, iterate the test by checking the affected URLs using the Googlebot user agent.
🔶 Step 1. Review Cloudflare rules and security settings
Please check the Cloudflare dashboard as mentioned earlier, especially the following areas:- Rules → Transform Rules → Response Header Transform Rules
- Security → WAF rules
- Any bot protection or firewall rules that may treat Googlebot differently
In some cases, such rules may unintentionally return a different response for specific user agents.
🔶 Step 2. Temporarily disable Cloudflare proxy
For testing purposes, please temporarily switch the domain record from Proxied (orange cloud) to DNS Only (grey cloud) in Cloudflare.After making this change, there is a possibility that the site may show an SSL error. This can happen because Cloudflare will no longer serve its edge SSL certificate once the proxy is disabled. There is no need to be concerned if this occurs.
To proceed with testing in DNS Only mode, you may need to re-deploy or reinstall the SSL certificate on the origin server so that the site can be accessed properly over HTTPS during the testing period. Once testing is complete, the proxy can be enabled again.
After that, test the URLs again using a Googlebot user agent. This helps determine whether Cloudflare is modifying the response.🔶 Step 3. Temporarily disable page caching plugins
If a caching plugin is active on the site, please disable it temporarily and test again. Cached responses or header rules can sometimes affect how crawlers receive responses.🔶 Step 4. Re-test using Google Search Console
After the above checks, run the Live URL Test again in Google Search Console and confirm whether the page can now be crawled without the X-Robots-Tag issue.🔶 Important precaution before making changes
I strongly recommend performing these checks together with your technical or server team to avoid any unexpected situation. Some configuration changes can accidentally bring the site down if done incorrectly.Please also avoid editing .htaccess or other server configuration files without taking backup. Also, this issue is certainly not related to robots.txt. Also note that .htaccess typically works at a directory level, so if the rule is not in the main directory, it usually does not affect the entire site. If needed, you may temporarily keep a default .htaccess configuration and test again.
🔶 Step 5. Advanced troubleshooting (only if the issue persists)
If none of the above steps help, please proceed carefully with the following:- First take a full backup from your hosting panel
- Temporarily switch to a default WordPress theme
- Deactivate plugins one by one and test the affected URLs after each step
This process helps identify if a specific plugin or theme is altering responses for Googlebot.
Regarding the sitemap failing to fetch, this may resolve automatically after the crawler response issue is fixed. Google sometimes takes a little time to refresh crawl status.
Please try the steps above and let me know the results. We can continue narrowing down the root cause based on what you find.
– GulshanHello @guffronmh30,
Thank you for reaching out. I am sorry to hear about the issue you are experiencing.
To begin with, please review the following setting in Cloudflare to ensure that a noindex header has not been applied unintentionally:
Login to Cloudflare → Select your Domain → Rules → Overview → Transform Rules → Response Header Transform Rules
Please verify that there is no rule adding a noindex directive to the response headers.
Additionally, during a quick review, I noticed that several pages on your site appear to be marked as noindex through x-robots which I was able to confirm. Please visit this Google Sheet to check a list.
You may want to review these pages and confirm whether the noindex directive is intentional.
In addition, it appears that every page listed under the skills-sitemap.xml sitemap is redirecting to your CW hosting provided subdomain. This behavior may also require urgent investigation on your end.
At this stage, I recommend performing a thorough audit of the entire site to identify the root cause and confirm whether these configurations are intentional.
If you require any further assistance, please share a specific URL where you are observing the issue. This will help us investigate the problem more precisely and provide more targeted assistance.
– GulshanForum: Plugins
In reply to: [Forget Spam Comment] Error 400 after clearing cacheHello @arcadeheroes,
I have reviewed your website and observed that the current theme does not fully adhere to standard WordPress development practices. Due to this, our plugin is not compatible out of the box.
However, if required, I can make it work through custom development tailored specifically to your setup.
Please contact me if you would like to proceed.
Thank you.
Forum: Plugins
In reply to: [Forget Spam Comment] Error 400Glad to assist. Thank you for confirming.
Forum: Plugins
In reply to: [Forget Spam Comment] Error 400Could you please try turning off the Jetpack commenting system? Our plugin is designed to work with WordPress’ default comments only.
Other plugins are not an issue. Kindly check below video
Forum: Plugins
In reply to: [Export and Import Users and Customers] Suggest Security EnhancmentI’ve experienced same issue. Fortunately, I deleted while manual inspection of files.
@webtoffeesupport Is there any update on this?
