Offering multiple feeds for the same entries is perfectly fine.
This is commonly done to provide different formats, or, like in your case, to offer a feed with the full content and a feed with excerpts only. Another reason might be to offer feeds with different entry count (e.g., the newest 10 items, and the newest 50 items).
Full content or excerpt?
Is it 'ok' to have IFrame tags in RSS feeds?
Well, as the error states, "interoperability with the widest range of feed readers could be improved" ...if the iframe tag was removed.
This is understandable since the main purpose of the iframe tag is to import external content from another site - this could literally be anything. Why would you want/need to do ...
I think a solution suggested by Tomalak should work universally. Ref: https://stackoverflow.com/questions/3805050/xml-parser-error-entity-not-defined
His solution was to convert character entities to corresponding numerical entities.
You could HTML-parse the text and have it re-escaped with the
respective numeric entities only (like: →  )...
It’s perfectly fine to offer multiple feeds. You could even offer multiple feeds for the same items, e.g., one for the full content and one for excerpts.
There is nothing that would have to be changed in a feed just because there exist other feeds. So an RSS feed’s channel element would contain the same content as if the feed were the only one.
You can't. This is textbook duplicate content. Either use canonical URLs, don't let the duplicate site be crawled and indexed, or don't duplicate the site. But definitely don't expect there to be anyway to have the same content twice without being penalized for duplicate content.
updated (which is required) must contain the date/time of the last significant modification (e.g., price change, added/removed features, etc., but not for corrections of spelling mistakes, or some unimportant change of a description).
published (which is optional) contains the date since when the product is added to the shop.
You must not change the id when ...
Much of this depends upon what country you are in. In the U.S., the law is quite clear.
Your scenario does not provide enough information. For example, do you have permission to use the RSS and images even if you do not cache them? The following should apply either way. Hopefully, the answer will be clear.
If you are using the image for commercial use (...
RSS (and Atom) are based on XML, so the issue you are having is that the & in the HTML entities isn't valid.
Typically you can solve this by double encoding the entities so that the & becomes &: &eacute;.
Most RSS readers will then unencode the first encoding, returning it to the original which is then handled by the HTML viewer.
why would anyone ever want to use CDATA blocks [...] ?
That's a good question.
I think the key is here:
since we are outputting a RSS document with a bunch of random content,
it can obviously very well contain ]]> somewhere
I don't use CDATA all that much (because I don't use XML all that much) but one place where I do use it is when I'm adding an ...
Yes, Google is very strict. It's hard to get listed. If you only have a blog then just say you are a blog.
There are guidelines and content policies available in the news publisher center
I'm being vetted at the moment
After a hard job, finally I find the reason and solution for above error and here I want to share it with others.
The reason for above error was blocking the crawl IP by firewall in the Cloudflare and it is not related to username and password in our feed configuration. If you face same error, first check the firewall setting in server and your Cloudfare. If ...
You should include meta tags in the <head> section of your pages with feeds:
<link rel='alternate' type='application/rss+xml' title='RSS' href='http://example.com/rss.xml'>
<link rel='alternate' type='application/atom+xml' title='Atom 0.3' href='https://example.com/feed.atom'>
This allows the feeds to be found. Some browsers make an RSS ...
There is no reason to assume that consumers would look at /rss.xml when they are looking for a feed. Feeds don’t have a reserved filename/location.
You would typically link your feeds from relevant pages, by providing a/area/link elements with the alternate link type and a type value of application/rss+xml (or application/atom+xml in case of Atom feeds).
Google recommends adding any rss feeds into webmaster for optimal crawling. An rss feed generally is a list of updates, and google can use this information to find new pages faster.
Here is a blog entry from google:
Product feeds are verified through matching against structured data on URLs, listed in product feed as product URL. If you activated automatic updates, so Google will prefer current structured data from the product URL. More here: https://support.google.com/merchants/answer/6069143?hl=en
Yes this is within the Googlebot ranges. Here is my list based upon past accesses. Please forgive the crude wildcards.
It's a formulae. You take the number of hits in period X and the period before X, and if it increased, it's trending.
Ofcourse, this is very simplistic. You should expand this to a few periodes, in which it should grow, and it should be over some threshhold (because going from 1 to 3 hits in 300% increase, but not trending).
The length of a period, or the ...