Read the documentation on how to use Yoast, for more info.
https://yoast.com/wordpress-robots-txt-example/

Should you link to your XML Sitemap from your robots.txt?
We’ve always felt it pointless to link to your XML sitemap from your robots.txt file, because you should add your sitemap manually to your Google Search Console and Bing Webmaster Tools accounts and look at their feedback about it. This is why our Yoast SEO plugin doesn’t add it to your robots.txt. Don’t rely on search engines finding out about your XML sitemap through your robots.txt .

https://kb.yoast.com/kb/how-to-edit-robots-txt-through-yoast-seo/

Download to your pc. Make sure you are only uploading the theme zip and not the all files zip.

WordPress does not support that normally. There might be a plugin for that. Website menus are intended to be ‘site wide’ which is how that has been done since 1994. However, some sites create sub-menus per page for sections of sites and often simplest way to do that is register a new widget area, then put that into a custom post template then create custom WP menu and put into the widget, then that widget area is loaded either from the custom template used for a site section as sub-menu.

To create custom menu “per post/page” might need way more customization.
Suggest:
a) look for plugin that does that
b) you might need to hire developer
c) be way more specific in what/why you are trying to do which is not a normal thing in WordPress, and not built in to any theme I’ve ever seen since 2004 for WP.

(I don’t work here; just some feedback as long time webdev dinosaur) 🙂

Some possible plugins might be
https://themify.me/conditional-menus
https://wordpress.org/plugins/page-specific-menu-items/

I guess some themes may now include this, but not common.

Try resaving your permalinks

If you have the proper meta data in the header of your posts, then it’s entirely up to Whatsapp to capture the content.

WordPress has built in ability to create a simple gallery …
https://codex.wordpress.org/The_WordPress_Gallery

if related to Google Search console error – it’s a ‘soft error’…

This is an ancient problem with WP and Google – when you update a theme, your redirects are temporarily without a place to go and this can cause the ‘index’ file to load in the theme folder, and be seen by Googlebot. The only way to avoid this when doing site updates is to use a ‘maintenance mode’ plugin which pretty much tells the world “we are temporarily closed to do updates” — the main culprit, and one I have complained to WP about for a decade is their use of an index.php file as the default template vs template.php — so there is always an index.php file in your root theme folder which anybody on the web, including Google, can go to and it will try to load and then *correctly* generate an error — it’s not a public page.

One option is to use an htaccess file to setup a redirect for that to your main URL, make the permissions unreadable by outside sources, etc.

Or, simply mark it fixed in search console and get on with your life.

This issue has been posted in this forum at least 100 times now, so obviously a note about this in the FAQs might be helpful ?

This is an ancient problem with WP and Google – when you update a theme, your redirects are temporarily without a place to go and this can cause the ‘index’ file to load in the theme folder, and be seen by Googlebot. The only way to avoid this when doing site updates is to use a ‘maintenance mode’ plugin which pretty much tells the world “we are temporarily closed to do updates” — the main culprit, and one I have complained to WP about for a decade is their use of an index.php file as the default template vs template.php — so there is always an index.php file in your root theme folder which anybody on the web, including Google, can go to and it will try to load and then *correctly* generate an error — it’s not a public page.

One option is to use an htaccess file to setup a redirect for that to your main URL, make the permissions unreadable by outside sources, etc.

Or, simply mark it fixed in search console and get on with your life.

This issue has been posted in this forum at least 100 times now, so obviously a note about this in the FAQs might be helpful 😉

Might not be issue, but disable any mobile plugin and just use theme as responsive for mobile.

Read the docs for Yoast, as good starting point. Most such plugins use a virtual robots.txt file.

Yep anything complex using a lot of javascript, custom fonts, columns, custom layouts, etc., are not intended for AMP. Again think “print friendly page” for slow mobile connection. So it comes down to basic UX think: if the “information” is most important, then AMP is great solution to not lose visitors due to page taking 30 sec to load.

This is why if *not* using AMP, it’s mission critical to “think” your post pages out as much as possible for speed with both Lighthouse check and Pagespeed check.

Muting is not something you can do via WordPress normally, as that is part of the video player, so you’d need to use a custom video player with option to mute video/audio. Likely need to look at a commercial plugin, or look at the audio player/video player plugins on wordpress.org in the plugin repository.

WP actually uses the mediaplayer.js library, so you have to include some kind of custom code for that …

discussion on audio volume topic here (this is related to playing audio, not video, but may be related from same library):
https://github.com/mediaelement/mediaelement/issues/2449

presumably you’ll need to do something like
startVolume: 0
via the javascript options.

Good luck!

Probably need to look online for an ad serving plugin that can insert ads on top of your own hosted videos, or as a ‘pre roll’ which are both fairly advanced topics.

Or, hire a developer to come up with something, as another option.

Heh. Yeah. I think it makes some kinds of content problematic, as we are selling services, so on our news pages, we also try to upsell people reading the news to use our services, which has diminished ‘experience’ on AMP.

I prefer a highly optimized responsive experience to AMP.

However, again, sometimes trying to read some websites like Autoweek with 50 stupid things loading, there is 30 sec delay sometimes to see first image, even on fast connection. So, there being able to just read article, see one photo, and couple of text only ads, would be preferable.

Nobody is obligated to use it, however, for some types of content on mobile, it can be beneficial.

I don’t think making the entire web ‘amp first’ is a good idea, contrary to what Google things. They do not own the web.

Welllll….. the main benefit is for slow edge connection mobile users; and since something like 80% of Google traffic is mobile, their thinking is that a slim line version of a page (stupidly it’s a lot like the old print friendly pages we used to do, so in many ways it’s ripping off the old school “simple print friendly version” page of olden timez).

For many things like company info pages, not useful as in a B2B setting you lose all the value of things like complex javscript elements and stuff like bootstrap layouts.

For our news pages we have 100 score with pagespeed and 100 seo score with lighthouse, running wordpress for the non AMP pages; so those work fine. However for our news pages, it is true the dumbed down version without our logos and branding and such, load faster if you’re on a phone with sloooooow connection, to not abandon the pages altogether.

So my preference is
> desktop – best experience
> desktop > responsive – iPad portrait, best experience
> mobile > resposive – best collapsing experience with same content/page materials
> dead slow in middle of nowhere visitor > AMP

on the other hand, why the hell would somebody want to read our news in the middle of nowhere on a connection that is one bar, and the speed is 1/50th normal?

So, on one hand it’s another stupid way of Google to put their ideas first, and on the other it’s useful for very slow connections, and if your content is useful in certain locations with slow internet for desktop, or 3G connections in general — it does make the page work. Still, they could have just said “hey, if you have print friendly page, we’ll drop back to that version…” and called it a day, which we’d been doing since 1996. (double sheesh).

Sorry, you asked 😉

Heh. Yeah. It’s one of the “stupid AMP tricks” (our sites were in the beta back in 2015, so have suffered through quite a bit with it… ).

Google will start checking. But good to resubmit your site maps via search console. When they are aware, it will show up and they will start poking you with error emails — some you can deal with, some will happen while you’re doing an update, and then next day “we couldn’t access two of your pages…” — which, of course, you were updating! LOL. So, then you resubmit those pages, then you get another email “we validated your fixes.” #SHEESH ! 😉

Theme does not control sending email. Just as heads up to those new to WP.
Email sent via WP by default goes via sendmail, or out via authenticated email via an actual account on server via correct port. However, this may require the plugin to ‘ping’ the account first before send, which may not work.

Another issue, is that if the email test from the plugin *does work* and you’re sending an email form from your website to @gmail, it might be going to the spam folder at the gmail account so never seen.

ABOUT WP Mail SMTP:
We went through this recently after server update and WP updates.

Suddenly, the latest version of ‘WP Mail SMTP’ would no longer work. All email tests would fail. (One presumes you are testing the email send option from plugin?) — we had to go back to 1.25 vs 1.3x — and that works. So, you may need to try different SMTP plugins to see which one *actually* works with your server.

Not sure that helps — but the SMTP plugin we’d been using since June 2016 stopped working Summer 2018, and we had to roll back to the prior version as “new version” simply did not work with WP forms, or with WooCommerce.

Upshot – if v 1.3 does not work, try to find 1.25 which does work.
Stupid I know, but we would have issue where one email test would work, then actual emails from form would not. Almost like our own server was blocking the plugin, so something changed from 1.25 to 1.3x.

Seriously, we’re running latest CentOS, Apache, https, http/2 and PHP 7.2x, no go with 1.3x but 1.25 works on two sep installs.

Try older version from github:
https://github.com/awesomemotive/WP-Mail-SMTP

https://github.com/awesomemotive/WP-Mail-SMTP/releases/tag/1.2.5

Try it 😉

Are you talking about a specific plugin, or the built-in video playback features in WordPress, which are not part of the theme?

Help with WordPress:
https://codex.wordpress.org/Video_Shortcode

Make sure you resave permalinks after enabling any AMP plugin, as that clears the rewrite transients and allows the dynamic redirect to work for that ‘endpoint’

Why not enter manually the final resolving urls in the menu? Wp allows to to put in any url, such as external sites, etc.

Did you install it ?
With NP 9 the ‘default’ page builder is TD Composer. WP Bakery VC is ‘optional.’
See the theme docs, but also the /plugins/ folder in the ‘all files’ download.

Not sure if that helps or not, just a thought. 🙂
( I don’t work here. )

For those who need it, why not try the plugin directions to add code to theme template to test?

Make sure your AMP endpoints actually work by testing in web browser yourself.

Try resaving your permalinks.

Check your Search Console account to see if AMP pages actually indexed.

• This reply was modified 7 years by simchris.

you may find this useful 🙂

https://forum.tagdiv.com/topic/tutorial-good-basic-security-practices/

a) check your setting in the main WordPress panel under ‘reading’ to make sure you don’t have ‘hide from search engines’ active
b) if using Yoast SEO (or other SEO plugin), make sure you don’t have a ‘post specific’ setting active to set page to ‘noindex’ *and* check to make sure you have your taxonomies checked ‘yes’ to be included in sitemap, otherwise they are marked noindex.
c) check the post does not have the setting in the post page from WP as ‘private’
d) check your htaccess file and robots txt files to ensure you don’t have any custom directives added to hide posts by URL, or ID
e) resave your permalinks; clear caching; optimize db

Theme does not control ‘hiding’ your posts/pages in any way.

Tags are not posts/pages, but only an index created from a post which has the tag added by you. You cannot edit the tag page, but you can delete it.

Typically the reason you might have tag pages set to no index is if you’re using a plugin like Yoast and have the setting in there to not add to site maps.

Similarly, this can also be controlled by separate site map plugin.

You can try disabling/removing Yoast SEO or other SEO plugin; delete any folder that the plugin created with redirects or similar.

Again — not managed by the theme; but by something *you* or your developer chose to do; so good to document this stuff when doing it, also make backups of your site before doing anything further.

Hope that helped, a little.
(I don’t work here.)

• This reply was modified 7 years by simchris.