<?php echo '<?xml version="1.0" encoding="UTF-8"?>'; ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" version="XHTML+RDFa 1.0" xml:lang="<?php echo $this->getLang() ?>">
Your done!
For the extension to have the maximum effect in terms of semantic richness, it is very important that you fill in EAN information on product level.
Note that is is only a W3C Working Draft at this stage, but should work nonetheless.
Magento has a quite bad habit creating sitemaps: It always puts the current date into the sitemap's lastmod field. This leads to poor crawl rates.
To fix this, follow these steps:
/** * Generate categories sitemap */ $changefreq = (string)Mage::getStoreConfig('sitemap/category/changefreq'); $priority = (string)Mage::getStoreConfig('sitemap/category/priority'); $collection = Mage::getResourceModel('sitemap/catalog_category')->getCollection($storeId); foreach ($collection as $item) { $xml = sprintf('', htmlspecialchars($baseUrl . $item->getUrl()), substr(Mage::getModel('catalog/category')->load($item->getId())->getUpdatedAt(),0,10), $changefreq, $priority ); $io->streamWrite($xml); } unset($collection); /** * Generate products sitemap */ $changefreq = (string)Mage::getStoreConfig('sitemap/product/changefreq'); $priority = (string)Mage::getStoreConfig('sitemap/product/priority'); $collection = Mage::getResourceModel('sitemap/catalog_product')->getCollection($storeId); foreach ($collection as $item) { $xml = sprintf(' %s %s %s %.1f ', htmlspecialchars($baseUrl . $item->getUrl()), substr(Mage::getModel('catalog/product')->load($item->getId())->getUpdatedAt(),0,10), $changefreq, $priority ); $io->streamWrite($xml); } unset($collection); %s %s %s %.1f
Legal Name -> Business name
This should hold the official name of the person or company operating the shop, e.g. “Miller Trading LLC”, even if the Web shop name was “diapers-online.com”.
Fill in the office address of your company.
POS Available ? => No
Same Pos address as company -> Yes
These two options allow exposing information about a brick-and-mortar store associated with the online shop. If you do not have a regular store, disable “POS”. If the address of the store is the same as the address you entered for the company, check “Yes” for “Same Pos address as company “. Otherwise specify the address of the store.
Short Description - > Fill in a short description about your offerings.
This is for consumers of the data that try to find a matching shop, not a particular product.
This indicates the types of audiences you are willing to sell to.
This is for setting the payment options you accept for all items in your shop.
This is for setting the delivery options you accept for all items in your shop. Note that if you use DHL or UPS at your discretion (i.e. the customer cannot choose), then it is better to check just “Freight”.
Strong Identifier Type -> EANUCC13
This determines the type of strong product identifier published for your items. EAN / UCC_13 / GTIN 13, ISBN13 / UPC are all names for the same identifier.
Only if you are using GTIN8 (“short UPC/EAN”) or long GTIN14 identifiers from the logistics you may want to change this option.
Use Existing Attribute ->
Magento has an existing attribute for product identifiers. If you check “Yes” in here, MSemantic will use that field for publishing EAN/UPC data. If you check “No”, Msemantic will use a proprietary additional attribute, which you will have to maintain for each product then.
Validity Period - > 3 months
Valid Through -> tomorrow
With these options, you indicate for how long your offers and prices can be assumed to be valid. Use the longest validity period that you can promise (they can be different for price and offer), because it can be that Google disables showing a price in a rich snippet if the validity period expires before Google will have re-crawled the page with an updated validity interval.
48 hours after the date and time of creating the page is the minimum that works well.