Strange SEO, Yoast or die…

After up to 0.9.48, problem still exists.

Simplest example.
blog name: “Sandbox”
tagline: “Just another WordPress site”
homepage title: “My Home Title”
homepage description: “My Home description…”

TSF settings: Title additions enabled, for homepage disabled.

ok, let’s try.
-normal: https://homely-salmon.w4.poopy.life/ -is ok, title is: “My Home Title”, desc.: “My Home description…”
-amp ver.: https://homely-salmon.w4.poopy.life/amp -omg ?? title: “Untitled | Sandbox”,
desc.: “Latest posts: Untitled on Sandbox”

*problem1: before <title> tag is unwanted auto generated meta description: <meta name=”description” content=”HOME HOME HOME Lorem ipsum dolor sit amet erat. Pellentesque tempus ornare varius, quam in…”/>
*problem2: title and description do not belong to static homepage, but like blog, for latest post (there is no posts)
*problem3: for homepage amp version title and desc. format should look like definied in TSF for homepage, not for others.

Next, another page https://homely-salmon.w4.poopy.life/other/ -ok, title: “Other Page Title | Sandbox”
description: “Other Page description…” -all right, according to the settings.
But on amp ver.: https://homely-salmon.w4.poopy.life/other/amp *problem1 still exists

sorry, *problem1 fixed by AMP > SEO settings (The meta tag that displays in head)

• This reply was modified 7 years, 7 months ago by infokurs.

@infokurs I assume you can edit wp-config.php at poopy.life?

Could you then add the following to it:

define( 'THE_SEO_FRAMEWORK_DEBUG', true );

I’m not sure if it also dumps debug data onscreen on AMP, but it’s worth a shot ??

If it doesn’t, you need to add a small snippet to your functions.php file as well.
Fair warning: This will crash your site if TSF is deactivated.

add_action( 'amp_init', function() {
	$debug_instance = The_SEO_Framework\Debug::get_instance();
	add_action( 'the_seo_framework_do_before_amp_output', array( $debug_instance, 'set_debug_query_output_cache' ) );
	add_action( 'amp_post_template_footer', array( $debug_instance, 'debug_output' ) );
} );

If you’ve done so, mention me and I’ll check the output.

I’ll also try this in the near future, but as I mentioned before: I can’t replicate the issue.

• This reply was modified 7 years, 7 months ago by Sybre Waaijer.

@cybr, now debug mode active. Yes, AMP version need snippet to work. ??

@infokurs Awesome! Thanks for activating that mode ??

I got all the data I need!

And, it shows the following:

is_blog_page => (boolean) true // This can never be true if is_home is also true <- wrong
is_home => (boolean) true // It's a blog?? <- wrong
is_singular => (boolean) true // It's also singular?? <- correct
page => (integer) 1
paged => (integer) 1
page_id => (integer) 0

While it should be:

is_front_page_by_id => (boolean) true
is_page => (boolean) true
is_real_front_page => (boolean) true // manipulation of is_front_page()
is_singular => (boolean) true
is_static_frontpage => (boolean) true // determining that the static front page matches the setting, i.e. 1251
page => (integer) 1 // pagination
page_id => (integer) 1251 // The assigned ID.
paged => (integer) 1 // pagination

What does it mean?
Well, WordPress assigned the home page as a static page…
But, on AMP the home page thinks it’s a blog. But that doesn’t exist, so TSF doesn’t know what to do.

With many fail-safes to prevent wrong output-data, it leaves you with this fail-safe title: “Untitled”.

I’ll dig into the AMP plugin (which hacks in the home page) to see what’s the culprit.

But you’ve definitely given us a great lead! Thank you so much ??

Before I go, could you tell me this?
If you go to wp-admin/options-reading.php, is the selection for “Posts page:” the following?

— Select —

If that’s so… well, even WordPress Core had many issues with that setting.
It’s cause for a very common bug (ergo is_front_page_by_id() and is_blog_page() within TSF).

Thank you so much, once again ??

Of course, “Posts page” is undefined ( -select- ).
Thanks too ??