It’s actually not an issue at all, it works just like it’s supposed to, be sure to submit the index sitemap though, not the individual ones, so submit sitemap_index.xml. See this screenshot for reference to show that it works:
I browsed through all the versions available here http://plugins.trac.wordpress.org/browser/wordpress-seo/tags/ and nowhere is there any “I” modifier. The “I” modifier is obviously invalid, thus the error. Updating the plugin will most certainly solve the issue. Or at least, if updates are not possible, edit line 476 of /wp-content/plugins/wordpress-seo/admin/linkdex/linkdex.php and turn $keywordCount = preg_match_all(“https://wordpress.stackexchange.com/”.$job[“keyword”].”/msIU”, $body, $res); or … Read more
wp_title() is filterable so there could be another plugin or most likely your theme already adding a filter. Have tried checking the force rewrite in the plugin options? If that doesn’t work you need to hunt down what else is adding the filter and remove it. If it’s your theme look in functions.php for add_filter(‘wp_title’, … Read more
You have two titles because Yoast adds an og:title tag, and then you add another one with your own code, what’s unexpected about this result? so remove the one you add with your code, problem solved. Facebook’s Debugger doesn’t like your page because you have two og:url tags, one added by Yoast, then another added … Read more
This text is probably being added to your feed by the “WordPress SEO by Yoast” plugin. In your admin panel menu, go to SEO, RSS. Delete everything in the box labeled “Content to put after each post.”
Your robots file as of right now: User-agent: Googlebot Disallow: User-agent: * Disallow: Disallow: /cgi-bin/ Disallow: /wp-admin/ Disallow: /wp-includes/ Sitemap: http://www.yadfaeq.com You aren’t specifying anything for Googlebot so you should remove it. Additionally, Disallow: could be interpreted as Disallow: / which would block your entire site. What your robots file should be: User-agent: * Disallow: … Read more
You are usgin an undefined $post->ID variable because there is no reference to any $post object in your code; instead, use the $post_ID variable retrieved in the function: function on_jobs_publish( $post_ID ) { global $wpdb; $wpdb->insert( ‘iCrewzWp_postmeta’, array( ‘post_id’ => $post_ID, ‘meta_key’ => ‘_yoast_wpseo_sitemap-include’, ‘meta_value’ => ‘always’ ), array( ‘%d’, ‘%s’, ‘%s’ ) ); } … Read more
In my effort to solve this I discovered a great resource for wordpress hooks for the job and found the right hook wpseo_saved_postdata here. Feel free to modify the code if you think it could be better. For now, it works for me. function set_noidex_when_sticky($post_id){ if ( wp_is_post_revision( $post_id ) ) return; //perform other checks … Read more
Normally, if there’s a WordPress file on disk, that’ll be served first directly by Apache or Nginx, before WordPress gets involved. This is done in your virtualhost config, e.g. in Nginx you’ll typically find the following, which tells it to try actual files first before letting index.php handle the URL and generate a page on … Read more
The solution should is this: add_filter( ‘wpseo_xml_sitemap_post_priority’, ‘my_custom_post_xml_priority’, 10, 3 ); function my_custom_post_xml_priority( $return, $type, $post) { if($type == ‘page’) { switch ($post->ID) { case ‘8’: case ‘395’: case ‘342’: $return = 0.9; break; case ‘5’: $return = 1.00; break; case ‘620’: case ‘703’: case ‘603’: case ‘688’: case ‘695’: case ‘614’: case ‘684’: case … Read more