You might do exaxtly what the error says, check the “user agent” for your site.

Check the htaccess file for anything weird, check the HEAD of your page source; check with your hosting provider to make sure site is sending correct headers.

E.g.,

= No cloaking found, = Cloaking found. You may need to check the site for the specific user-agent.

“user agent” is the important note there. The concept of cloaking in this context refers to:

SEO Cloaking Checker
http://www.seotools.com/seo-cloaking-checker/
The SEO Cloaking Checker detects whether a Web site uses "cloaking," a server technique that some sites utilize to try to fool the search engines into awarding rankings the Web pages do not deserve. Cloaking involves showing one version of a Web page to users and a different version, usually stuffed with other keywords, to the search engine spiders. This is a stealth method that Google and the other search engines consider deceptive, since it attempts to bias the spiders into ranking the Web page undeservedly higher or for a different keyword term. We strongly discourage using this type of technique since it is spam, and if detected, could cause your Web site to be penalized in the search engine results.

So, if you have something changing the “user agent” string in your HTML pages, that would be bad; or some wonky thing in your htaccess or robots.txt file — that would be bad.

As far as malware, you can also test with this:
https://www.google.com/transparencyreport/safebrowsing/diagnostic/

Hopefully it’s a non issue.

You might do a Google search for the issue, which is usually best thing to do:

e.g.,

https://wordpress.org/support/topic/cloaked-site

============================

Upshot means “in conclusion” … it’s not a theme issue, so something you have added to your site means things YOU have added like a plugin — the theme doesn’t add plugins to your site, you do.

SO you need to debug what you’ve done to the site that caused the issue. If 10,000 people don’t have an issue, and you do — it’s pretty obvious that something you “added” (meaning, install a plugin, add javascript code, etc.) is causing the issue.

The only way to debug is to turn stuff OFF until you figure out what it is; remove stuff you added like custom javascript loading something from elsewhere, etc.

If something is being “cloaked” by a plugin — whatever that actually means — then it might be an issue, might not be. What is the exact meaning of “cloaked” in this context? For example hiding a menu from desktop, and only showing it for mobile users, might technically be “cloaking” or “hidden” until needed.

If something is hidden “behind” something and not see to visitors but is loaded in the browser, that is a problem as that is how malware is hidden, such as an on click event behind a login box, etc.

Best of luck.

• This reply was modified 10 years by simchris.

I’d likely just use file found in the Newspaper all files download, upload that as a folder via FTP, then follow these directions
https://forum.tagdiv.com/the-child-theme-method/

You don’t need to ‘create’ the base child theme, it’s included in the theme ‘all files’ downlaod.

Sorry if that didn’t help.

Nobody else having this problem I am aware of. Not theme related.

Did you
a) try turning off plugins except VC to determine a bad plugin?
b) did you scan your site with SECURI? – https://sitecheck.sucuri.net// — it found no issues when I just checked.
c) did you check your Google webmaster tools account for alerts about issues? If Google not having an issue, likely a non issue.
d) note some SEO testing tools online are worthless

When I just checked one of your posts you have a popup that floats over page asking to login with Facebook ? That sure isn’t normal (fanbox popup).

Possibly Wordfence code conflict ?
Possible bug in disqus ?

=====
You didn’t need to create new post, you could simply update the original thread.

Upshot – not a theme issue; but issue with something YOU have added to site on top of theme.

I think you can turn this off in the theme panel from post settings ?

well, obviously you need to have imagemagik/GD library running on your server to make images; your image folder needs to be “writable”

— the featured image will be added once story is “published” and will show on the post page bottom right as featured.

If you add the https to the wp-config.php you likely don’t need the htaccess addition; just resave permalinks.

As WordPress should automatically rewrite all requests to https, based on seeing in the config that all pages should load as https.

Sorry, we have mix of static and wordpress, hence we need that addition.

For “only wordpress” the built in rewrite rule written by WordPress to the htaccess file will work, once you save your permalinks.

I think it’s on THemeForest/Envato for maybe $8 and totally worth it — we use it on 6 websites with no issues.

It’s an adventure, sadly 🙂

Did you add the explicit link to your https website in your wp-config.php file ?
https://codex.wordpress.org/Editing_wp-config.php

define('WP_HOME', 'https://www.mysite.ooo');
define('WP_SITEURL', 'https://www.mysite.ooo');

*(we use www – you might not be; but that has to be consistent too – either all www or no www; not both)

And “obviously” resave your permalinks from wp admin panel after you add that. Clear cache. Clear transients!

I’m using Apache, so if you’re using something else not sure my htaccess code will help, but here is what we use for global https redirect:

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,QSA]
</IfModule>

Google article if not already read
https://support.google.com/webmasters/answer/6073543?hl=en

• This reply was modified 10 years by simchris.
• This reply was modified 10 years by simchris.
• This reply was modified 10 years by simchris.
• This reply was modified 10 years by simchris.
• This reply was modified 10 years by simchris.

Upshot, some “SEO testing tools” are total B.S. and are often scams to sell you a subscription to their “scanning service” or somesuch, or have not been updated for modern HTML5, Boostrap, JSON, etc. and so “get confused.”

We use Auto Post Thumbnail PRO which works perfectly the past 2 years with Newspaper / Newsmag. 🙂

What helps immensely is
a) make sure you change your site URL to https in the WP site setting (obviosuly)
b) add an explicit setting for the URL in the wp-config.php file for https (path to site)
c) use wp-optimize to clear all “transients” and clear all other cache
d) make sure you set up a site-wide 301 wildcard redirect in your htaccess so any request for http actually loads https version for “anything”

Any theme stuff should “pick up” the https setting if you put it into the wp-config.php file. (In theory.)

We did this in Nov 2014 and went through some of the same issues.

Disqus can slow down the site and page speed.

There is alternate plugin many of us use/used which uses the Disqus API but loads things after main page content loads for better speed.

There have also been reports of many issues with Disqus in 2016. Some folks are choosing to move to FB comments. Others are just sticking with the builtin WP comments. Others still are removing comments entirely as not adding to the conversation on many sites, and simply pulling in trolls and spambots.

Best method is to actually follow Apple guidelines, and upload the various sizes into the ‘root’ of your website, and Apple iOS will automatically “look” for those, just like a favicon.ico does not technically need to be in the meta data either.

https://developer.apple.com/library/ios/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html

Yeah! Sorry, i don’t work here, so don’t have all the links to ‘docs’ in hand 🙂

We have style 5 as ‘default’ then use style 2 for news posts that pull in featured image.

I had asked for a new style – basically ‘2’ without photo to use as default, but I was in minority on that 🙂

Been too busy to hack it (not that hard) to make a style 25 …

but hope that works for you.

• This reply was modified 10 years by simchris.

I guess if you have an account/membership system running on your website, and while you’re logged in it will show your account info. That is usually managed by whatever account system you have in place, like a store, or bbpress, or similar.

Tip: try making a new user account, then login as THAT user to see what sites looks like as non super user, such as an ‘editor’ or ‘contributor.’

Leave featured images = on. You need them for thumbnails, OG tags, and new posts with images not placed.

Go to template settings for posts, set ‘default’ to the template with no photo (look at the little thumbnail graphics of different template layouts – one has no photo).

With new posts, on the post page, choose a custom template which does have a photo, which will pull the featured image.

This was what I did, since we had 10 years of content with images placed “on the page” already to not get duplicate images.

Try it 🙂

What we do:
choose the default template without photo for existing content, then manually choose one with featured image for new posts.

Do you mean the WordPress black admin bar?
That is part of WordPress, not the theme.

It shows whomeever you are when logged in.
You can disable per user under WP admin > users

I’ve found that stuff like wp-optimize works better for simple “optimization” — but any REAL edits to dbase should be done via phpmyadmin on server, and learn to delete ONLY the table rows in the dbase that are causing bloat, such as from a former hit counter, or some funky old plugin polluting the database. Luckily lots of tutorials online for this, just a pain in the butt to “focus” on scannning through tables.

I did this recently for one of our 11 year old sites, where the dbase was just freaking huge, and there were some old things in there that the “bad plugins” didn’t gracefully remove on exit, or have option to scrub prior to deactivation.

Just a comment, since I was lurking here a little while 🙂

This seriously needs to put this in a FAQs page ! 😉

We put ours at bottom of the single template being used for our posts as default, and then the one other template being used for older content (where photo was already in the post). We only track posts, hence our reasoning there.

Note for tracking /AMP pages, we’re still testing the single pixel image tracker instead.

If you’re setting up PIWIK you should know what I’m talking about 🙂

Well.. if you want folks to try to help your issue, perhaps help provide some info ?

What tool is saying you have a cloaking issue ?

Link to show the error, screenshot, proof of issue, what you did to debug or fix? Did you try rolling back your changes to a backup to not get the error?

Nobody here can ‘guess’ to what might be happening as that is not a normal issue for the other 20,000 installs of the theme.

But I don’t work here, so just ignore me. I’m out 🙂

https://support.google.com/webmasters/answer/66355

You need to put the full URL for your FB page, not the partial one.

A URL includes the http or https to make an actual “URL”

e.g.,

https://www.facebook.com/Send2PressNewswire/

• This reply was modified 10 years by simchris.