kaj69

Same for us too, WP 6.6 and Restaurant Reservation 2.6.24

Sorry for erronous link – the correct is https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/matomo/matomo-analytics-511-cross-site-request-forgery-to-notice-dismissal

It could be about the same issue but it warns for 5.1.1(???)

Wordfence WAF warns for a Cross-Site Request Forgery (CVE-2024-38766) in versions up to, and including, 5.1.1 and no known patch available.

Will a new patch be expected or should I deactivate/delete the plugin.

From v3.5.1.1 to v3.5.2 on WP v5.3

Same here, to delete entries older than 6 months.

Thanks for your rapid reply – this is what I call “High Quality Service”!

Another +1 for this functionality. ETA?

Hi @cybr

Once again, thanks for your rapid reply. You write “the only way to truly validate…” and Google actually says “No errors found” so I second your assumption that the alternative checker used is invalid.

I will re-activate “WP Rocket” (v2.9.11) and submit the sitemap to search engines once again and do a follow-up at each engine within a couple of weeks.

BTW, I’m very impressed of your support and the speed of your replies – very professional!

Thanks once again.

@cybr

You’re absolutely correct – the firewall was configured a little bit too tight, I have now changed it.

I’m also using the cache plug-in “WP Rocket” where I had ticked the options to minify HTML, CSS and JS but I have now removed all those items.

I even deactivated all plugins except TSF and ran the Site Audit.

But, the result was the same in SEMrush: Sitemap has format errors.

And, when using the tool SEMrush uses, the https://www.freeformatter.com/xml-validator-xsd.html, and pasting in the sitemap then I receive:

S4s-elt-character: Non-whitespace Characters Are Not Allowed In Schema Elements Other Than 'xs:appinfo' And 'xs:documentation'. Saw 'Document Moved'., Line '1', Column '28'.
The Markup In The Document Following The Root Element Must Be Well-formed., Line '2', Column '2'.
The Markup In The Document Following The Root Element Must Be Well-formed.

If I manually remove some of the lines in the beginning of the file (see above what is kept) then it passed the validation, howcome?

@cybre and @harryshawk

Thanks once again for your invaluable information, it has given me a completely different view of focus keywords. Previously I had the impression that the focus keyword field of Yoast alone was a dedicated, “secret key” for ranking high in SERPs, as a “type-and-forget”.

Now I realize that focus keywords are still important but should be addressed in the content in a more naturally way.

@harryshawk and @cybre – Thank you VERY much for the information!

I was in the belief that focus keywords was the #2 issue to focus upon (after the content quality) and spent quite a lot of time upon this but realizes now that it’s not. You’ve pushed me into another path of thinking for which I’m very grateful.

Once again, thank you very much ??

Kaj

Sorry, have now asked the question in a new thread.

Hi cybre,

Yoast (and others) do often emphasize the importance of “long tail keywords” and Yoast has a dedicated field for keywords. Aren’t these used at all in SEO Framework or…?

Brgds,
Kaj