• Resolved pixelboxstudio

    (@pixelboxstudio)


    My site https://www.pixelbox.in was working fine until I installed “Wp Super Cache” plugin. I have deleted this plugin.
    Now it’s been causing problem to Yoast plugin results. Google is not accepting the sitemap
    and error message is “Your Sitemap appears to be an HTML page. Please use a supported sitemap format instead.”

    If I am not wrong the site is still getting routed to index.html but not to index.php
    How to remove html pages from “Cache” folder from WP-Content folder as it doesn’t accept
    CHMOD 777 ? Is there any script I can enter in the “Custom CSS” plugin that I use ?
    Well I am not a programmer. You can investivate the problem and suggest as it looks
    like it’s blocking Yoast and when the existing site has disappeared from Google.

    https://www.ads-software.com/plugins/wordpress-seo/

Viewing 15 replies - 1 through 15 (of 17 total)
  • Are you certain that you uninstalled SuperCache correctly:

    To manually uninstall:

    1. Turn off caching on the plugin settings page and clear the cache.
    2. Deactivate the plugin on the plugins page.
    3. Remove the WP_CACHE define from wp-config.php. It looks like define( ‘WP_CACHE’, true );
    4. Remove the Super Cache mod_rewrite rules from your .htaccess file.
    5. Remove the files wp-content/advanced-cache.php and wp-content/wp-cache-config.php
    6. Remove the directory wp-content/cache/
    7. Remove the directory wp-super-cache from your plugins directory.

    Also, try to refresh the sitemap with disable >> save >> enable >> save

    Thread Starter pixelboxstudio

    (@pixelboxstudio)

    Thanks you and it seems to be working. Will be certain about search results in couple of days.
    But few queries ..
    * Is caching a super safe for WordPress and search result ?
    * As per reviews ” WP Super Cache” is too much problematic.
    * If caching is recommended then which plugin is safe to install and unintall without disturbing a codes of WordPress and it’s files ?

    Happy to hear that.

    In answer to your questions, most webmasters use a caching plugin to improve performance. Here is a useful review of (most of) the available plugins: https://wpdevshed.com/best-wordpress-cache-plugin/

    Regarding SuperCache, I’ve used it for 4+ years with any problems. Note that with any caching plugin it is important to *exclude* the sitemaps from caching. In SuperCache you can do this via SuperCache >> Advanced >> Accepted Filenames & Rejected URIs >> Add here strings (not a filename) that forces a page not to be cached:

    sitemap_index.xml
    post-sitemap.xml
    page-sitemap.xml

    Thread Starter pixelboxstudio

    (@pixelboxstudio)

    Thanks Barnez. I am just wondering why the site disappeared all of a sudden from Google ? Once SuperCache was installed and after cleaning up, it’s visible now ,

    No idea. It could be because you needed to exclude the sitemap_xml strings from caching, and Google didn’t like the cached version. If you’re concerned about SuperCache, why not try one of these, making sure that your exclude any strings associated with your sitemap from caching:

    https://www.ads-software.com/plugins/zencache/
    https://www.ads-software.com/plugins/wp-fastest-cache/

    I wouldn’t use cache plugins. Better do this yourself in htaccess file

    After that you combine all of the javascript
    Combine all of your CSS

    Minify CSS and Javascript with a minifier

    Run your website again

    It will load minimum 1 second faster than with any cache plugin on the market

    A good source to combine javascript and CSS step by step is found here

    Thread Starter pixelboxstudio

    (@pixelboxstudio)

    When I am submitting my site map to Google, I am getting this error again
    through boath Yoast and Google XML..
    “Your Sitemap appears to be an HTML page. Please use a supported sitemap format instead.’
    As instructed earlier, I had deleted all files of “WP Super Cache” and changed few codes as well. Is there anything left in https://www.pixelbox.in

    Can you enable the sitemap through Google XML Sitemaps and post a link to it.

    Thread Starter pixelboxstudio

    (@pixelboxstudio)

    I tried Google XML Sitemaps too but this too gave same error.

    I have just installed WP Super Cache now I am thinking I should get rid of it. In the Add here strings (not a filename) that forces a page not to be cached: there is

    wp-.*\.php
    index\.php

    Should I leave them there and add the other 3 or delete them and add the 3 new ones that are in the answer above.

    As it looks like there is not changing content on the site (e.g. blog), why don’t you try manually creating an xml sitemap and uploading it to the root of your site (again, exclude the string from any caching plugin that you may be running):

    https://www.xml-sitemaps.com/
    https://www.web-site-map.com/
    https://xmlsitemapgenerator.org/

    Then see if GMP is happy with the file when you test it in the console.

    I have a sitemap that is submitted by Yoast already and I was just wondering if I need to make any adjustments to WP Super Cache to bypass any dramas.

    Sorry for the questions but I am a complete noob.

    @wplearner01

    As mentioned above, it is important to *exclude* the sitemaps from caching. In SuperCache you can do this via SuperCache >> Advanced >> Accepted Filenames & Rejected URIs >> Add here strings (not a filename) that forces a page not to be cached:

    In that option insert the string of the main sitemap index and all page/post/tag etc sitemaps. For example:

    sitemap_index.xml
    post-sitemap.xml
    page-sitemap.xml

    Leave those the pre-populated exclude strings in place:

    wp-.*\.php
    index\.php

    Thread Starter pixelboxstudio

    (@pixelboxstudio)

    Some warning about this plugin as issued last year at https://bit.ly/1Gx0EfA
    @wplearner01..Remove the plugin. It creates problems for search engines and can’t wipe it off at one go.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘WP Super Cache blocking Yoast’ is closed to new replies.