My blog rss feed is located at - Online Income Startup
http://www.onlineincomestartup.com/
But the feed is not being detected in some sites. Please guide me on how to fix the feed to make sure everything is working fine.
try add this in the head tag:
<link rel="alternate" type="application/rss+xml" href="http://www.onlineincomestartup.com/feed/" title="Online Income Startup" />
Related
I am using WPML for my multi-lingual wordpress site. I am having an issue getting the hreflang attribute to be implemented properly.
According to this article:
https://support.google.com/webmasters/answer/189077?hl=en
The hreflang tag must include not only the url of the translated page, but also the url of the current page. For example, when I am on https://example.com the href tags should be as follows:
<link rel="alternate" hreflang="en" href="https://example.com" />
<link rel="alternate" hreflang="de" href="https://example.com/de" />
This seems to be the correct implementation, however when using WPML v 2.9 only the translated hreflang tag is displayed. For instance when I am on https://example.com it only shows the following:
<link rel="alternate" hreflang="de" href="https://example.com/de" />
I have ticked both options in WPML > Languages > SEO Options:
x Display alternative languages in the HEAD section.
x Add links to the original content with rel="canonical" attributes.
Perhaps I have misunderstood and having a canonical tag like this:
<link rel="canonical" href="https://example.com/" />
will suffice as the current page's hreflang tag. Thanks for any input.
I'm using WPML v3.1.8.4 and it's working fine for me. Can you try upgrading to the newest version?
I guess this may be a conflict between WPML and another plugin - seems WordPress SEO. I saw it somewhere in WPML Support Forum
If you are using Yoast Wordpress SEO and WMPL, juste add the following in your functions.php
add_filter( 'wpseo_canonical', '__return_false' );
I am just about to launch an eCommerce site using WordPress and WooCommerce and trying to tidy up the source code and strip out all the WordPress header lines.
The site is pure eCommerce with a blog for users and search engines, I believe the functions below are for a pure blog website.
<link rel="profile" href="http://gmpg.org/xfn/11"/>
<link rel="pingback" href="http://www.domain.co.uk/xmlrpc.php"/>
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://www.domain.co.uk/xmlrpc.php?rsd"/>
<link rel="wlwmanifest" type="application/wlwmanifest+xml" href="http://www.domain.co.uk/wp-includes/wlwmanifest.xml"/>
Does anyone know what is required from the above for WordPress to function? And how we can remove these from WordPress, if we can?
Thanks Kindly.
J
You can safely remove all of these from your header.php file. They aren't required for the site to function.
More info: In HTML5, the "profile" attribute was dropped.
The others are purely optional.
For de-registering the bottom two, you'll need to add some new lines to your functions.php:
remove_action('wp_head', 'rsd_link');
remove_action('wp_head', 'wlwmanifest_link');
These functions, from the wp_head action hook, can be viewed in wp-includes/general-template.php, starting on line 2190.
From this file, rsd_link "display(s) the link to the Really Simple Discovery service endpoint."
The wlmanifest_link "display(s) the link to the Windows Live Writer manifest file." If you don't use Windows Live Writer, there's no need for this.
First thought was to include the link tag in my theme. If a theme can be used: which content type do I have to use?
If a theme cannot be used: where do I put the link tag?
Used it before, sorry, didn't recall #facepalm
How to do it:
Place the code manually in the resource section of your Xpage/Custom control as you are not be able to compute the href value:
<xp:this.resources>
<xp:linkResource rel="alternate" type="application/rss+xml"
title="Oliver Busse - OSnippets"
href="/#{javascript:config.getConfig().getItemValueString('pathSnippets')}/rss.xsp">
</xp:linkResource>
</xp:this.resources>
I'm Trying to display a RSS link to a blog post in Orchard 1.5 (should be simple right)
I feel I must be missing something here :
The documentation here seems out of date? I can't find any instance of the Html.RegisterFeed or Html.FeedLink in my current Orchard 1.5.1 codebase.
I can see the <link /> tags have been inserted into the Header section of the page.
<link rel="alternate" type="application/rss+xml" title="News" href="/Riders/rss?containerid=85" shape-id="334">
And I'm looking at the View in Orchard.Core/Feeds/Views/Feeds.cshtml and I can see
#Model.FeedManager.GetRegisteredLinks(Html)
But I don't know how to get this to render on my page, ideally in First aside section.
Could someone point me in the right direction.
For instance
I want to put something like
RSS feed
and it would render
Searching for the correct answer all day, and nobody seems to know, so I thought I'd give it a shot here as a last effort before I keel over.
FeedBurner's SmartFeed service does this:
Translates your feed on-the-fly into a
format (RSS or Atom) compatible with
your visitors' feed reader
application.
Based on the above information, which would be correct to add to my <head> section? The difference being the type="foo" sections?
<link rel="alternate" href="<?php echo feedburner_url(); ?>"
type="application/rss+xml" title="FooBar RSS News Feed" />
or...
<link rel="alternate" href="<?php echo feedburner_url(); ?>"
type="application/atom+xml" title="FooBar Atom News Feed" />
or possibly even both?
Can't find the answer anwywhere. Google (owns FeedBurner), Google groups, FeedBurner help, etc. And FB conveniently doesn't have any type of help system. Maybe that's a hint? =)
I'd think you could use either or both at the same time.
What should happen is that the user's feed reader will make an HTTP request with the 'Accept:' header indicating what type of feed it wants (application/atom+xml or application/rss+xml). Feedburner would then look at the Accept header and serve up the appropriate type for you.
I think you are fine with putting both up. Feed readers are smart enough nowadays to figure out how to get the feed in a format it can easily use.