FoF Sitemap

rob006

clarkwinkelmann The questions then is, do search engines prefer to have as few sitemaps as possible, or do they don't care if we have one set for each data type ?

I don't think they care - this is common practice to split sitemaps into smaller batches, and every medium-sized website needs to do this. You can also provide lastmod for sitemap listed in index, so spiders should be able to detect which sitemap needs to be checked again - even if you have 10s of sitemaps in index, google bot should focus only on these recently changed.

ProgWeb

It seem that Google Webmaster do not support the format of this sitemap !

I import it normally but one minute later Google say that they can't fitch datas of the sitemap.

clarkwinkelmann

ProgWeb I tested it working fine, albeit a few months ago.

Could you share the exact message Google tells you or a screenshot ? From the way you describe it, it sounds like it could also be that your server failed to answer to Google.

Also what is the size of the sitemap ? (number of discussions ?)

matteocontrini

It's working fine for me as well

[deleted]

clarkwinkelmann it sounds like it could also be that your server failed to answer to Google

You should also check and see if your webserver has WAF enabled. If it does, then this often blocks crawlers by default.

ProgWeb

@clarkwinkelmann Here a screenshot about the error returned by Google:

When I access directly the sitemap link, it is working ... only Google that have difficulties to fetch it.

clarkwinkelmann

ProgWeb it looks more like a proxy/firewall issue then, as suggested by mcutting above.

If the extension returns no error when the sitemap is accessed directly, there's not much we can do here.

BloveDawn

I'm using Apache 2. Can you provide this rewriting rule?clarkwinkelmann

clarkwinkelmann

BloveDawn which rewrite rule ?

No special rule should be needed for this extension to work. The rule about nginx in the README solves a rare case found in only some nginx servers.

If you encounter an issue while using the extension, please share the relevant error logs.

nitaaikumar

Dear @clarkwinkelmann, Please add an option to not include the user profiles pages in the sitemap.xml. If there are thousands of users, does it not create a lot of SEO noise and plus duplicate repeating of the posts on the user profiles also? I added Disallow: /u/ in my robots.txt and added the sitemap.xml to Google. But now Google Search Console is showing the errors that all the user profile pages have been blocked by robots.txt. In order to remove this error, I will either remove the disallow in the robots.txt which I don't want to, or there should be a way in the sitemap.xml to remove the user profile pages.Have canonical tags been added to user profile pages like tag pages in Beta 10? Thanks.

clarkwinkelmann

nitaaikumar right now the sitemap reflects what is visible to guests. So if guests can see profile pages, they are automatically included in the sitemap. If you prevent guests from seeing profiles through the permissions, they will also disappear from the sitemap.

I have no idea how positive or negative it is for search engines to receive links to all profiles.

FBI

clarkwinkelmann Thanks for info.
I've found thousands from my forum 😃

julienlg

Hello,

I use Freeflarum and the Flagrow Sitemap extension.
But I have a Nginx 404 error; any help to help me to fix that problem ?
Regards

clarkwinkelmann

julienlg have you tried the "If you are running nginx" instructions from the first post ?

julienlg

FriendsOfFlarum
If you are running nginx, it's possible that /sitemap.xml will return the 404 error of nginx instead of being handled by Flarum. In this case you can try adding the following line to your site config, below the location / {} block of Flarum or at the end of the config. See posts below where we discussed this fix for more details.

location = /sitemap.xml { try_files $uri $uri/ /

i use Freeflarum so I do not have access to my config.php file

clarkwinkelmann

julienlg please contact FreeFlarum support via email or write in the FreeFlarum discussion.

duongkimngoc

FriendsOfFlarum
hi, thank you for your work.
I'm having this issue after install sitemap extension.
I'm using Flarum beta 11 and even after I add the nginx conf, I still get 404 when open sitemap.xml

server {
        server_name www.mysite.com;
        listen 80 ;
        access_log /var/log/nginx/access.log vhost;
        return 301 https://$host$request_uri;
}
server {
        server_name www.mysite.com;
        listen 443 ssl http2 ;
        access_log /var/log/nginx/access.log vhost;
        ssl_session_timeout 5m;
        ssl_session_cache shared:SSL:50m;
        ssl_session_tickets off;
        ssl_certificate /etc/nginx/certs/www.mysite.com.crt;
        ssl_certificate_key /etc/nginx/certs/www.mysite.com.key;
        ssl_dhparam /etc/nginx/certs/www.mysite.com.dhparam.pem;
        ssl_stapling on;
        ssl_stapling_verify on;
        ssl_trusted_certificate /etc/nginx/certs/www.mysite.com.chain.pem;
        add_header Strict-Transport-Security "max-age=31536000" always;
        include /etc/nginx/vhost.d/default;
        location / {
                proxy_pass http://www.mysite.com;
        }
        location = /sitemap.xml { try_files $uri $uri/ /index.php?$query_string; }
}

clarkwinkelmann

duongkimngoc is it a Flarum not found error or an nginx not found error ? You should be able to tell by the presence of a "go back to homepage" link (if there's a link, it's Flarum).

youngseebi

My forum runs in a subdomain. Therefore, the sitemap will be regenerated in http://underforums.com/forum/sitemap.xlm. Should I somehow make it appear in the root (http://underforums.com/sitemap.xml) or it doesn't matter?

Thanks

[deleted]

youngseebi As long as the sitemap can be parsed, and you tell Google where it is, it won't matter.

« Previous Page Next Page »