I have 2 wordpress installs under main domain.
www.example.com --1st wordpress install
www.example.com/blog --2nd wordpress install
What is the best way in wordpress to generate a sitemap for submitting my website to google such that there is no sitemap conflict and SEO penalty for such a setup?
I use yoast plugin and would not mind using other plugin to generate a sitemap. My concern being, will www.example.com sitemap plugin account for the wordpress install in the sub-directory /blog? what if I use the same plugin in both wordpress install. Will there be a huge conflict?
Please suggest the best way to generate a sitemap to help submit my site to search engines.
Thank you very much in advance.
Best,
It's ok.
You'll have 2 sitemaps:
www.example.com/sitemap.xml
www.example.com/blog/sitemap.xml
Just submit both to Google Search Console.
Related
Currently a TYPO3 website of ours has had a complete revamp and we would like to redirect all the old URL's in Googles index to the new existing URL's
For regular pages I used the new site management tool (Redirects) in TYPO3 v9. However what is left is the old indexed links of the content.
www.websitename.com/content/docs/this-is-my-document.pdf and so on. Including images and other miscellaneous links to files.
Now what would be the best way to redirect those links?
I could use htaccess ofcourse or is there something in the TYPO3 core/Extbase what I could be able to use?
I would always prefer redirects with mod_rewrite in the .htaccess file since it's much faster than any TYPO3 solution. If the redirect is done via .htaccess, there is no need for the webserver to invoke PHP or the database. Thus it's faster.
Found out we stopped rewrites by default for URL's with:
RewriteRule ^(typo3/|content/|typo3conf/|typo3temp/|uploads/|favicon\.ico) - [L]
By removing the 'content/' I was able to use the redirect functionality from the core. This was done so we could manage redirects through the TYPO3 enviroment in the future.
as Peter said above it would be faster to use .htaccess but we would like for it to be more manageable in the future through the system. So we chose the core option.
I'm running a mediawiki installation with a "nice" URL htaccess to show https://example.com/Wiki/Page
I'd like to enable localization and translation on subdomains.
I'm thinking https://fr.example.com/Wiki/Page displays content from https://example.com/Wiki/Page/fr, and https://fr.example.com/Wiki/Page2 displays content from https://example.com/Wiki/Page2/fr
I think that should be achievable with .htaccess, but I'm not a mediawiki expert. Is there anyone out there that can help with enabling mediawiki translations on a subdomain like the above? I think it's just an .htaccess question, but not sure what it might break with mediawiki too :)
I understand that .htaccess is not supported by GitHub Pages. Is there an alternative for password-protecting particular directories for websites hosted by GitHub Pages?
Although you can't use .htaccess or .conf, Github has instructions on how to use the Jekyll Redirect From plugin.
https://help.github.com/articles/redirects-on-github-pages/
The page above no longer has any mention of the plugin. The direct link to the jekyll-redirect-from plugin GitHub repo is https://github.com/jekyll/jekyll-redirect-from
"Unfortunately, GitHub pages only supports static pages. There is no way to make it execute server-side code and thus it's impossible to protect your pages with any kind of authentication scheme. If you expand further on why you need to password-protect your pages, maybe I can help you find a workaround."
Source: https://webapps.stackexchange.com/questions/35692/is-there-an-alternative-to-using-htaccess-to-password-protect-subdirectories-in
I'm using a 404.html to redirect users from old S9Y index.php to my new blog on Github Pages. Check this commit: https://github.com/lionello/lionello.github.io/commit/c175f6524a53e29aea1890c8a758afd0e8944852
This post comes out at the top of web search when you look for .htaccess redirects in github pages. I am going to answer this question in that sense.
One option is to use a DNS redirect instead. You do this by putting a file named CNAME in the project's root directory (not sure if it works in a subdirectory). Just put the redirection URL in the file. However, there are a few limitations, e.g. you can only redirect to a website's root.
The answer is yes you can now add "404.html" in you code Repository. You can display a custom 404 error page when people try to access nonexistent pages on your github site.
For more information you can refer to this link!
I want to add a robot.txt so my web page can be found...
So I have heard that putting a robot.txt with meta tags in the root of my site can do this.
Is this true?, if so,
What would be the steps to add or generate this robot.txt?
I have found this
Robots.txt is more for telling the crawlers where to and where to not go once they've already reached your site.
A better way to get crawlers onto your site is to build a sitemap for your site, then use Google Webmaster to submit this sitemap to google. You'll also want to include the sitemap on your site's root url and tell google where it is (all of this can be done in Google's Webmaster Tool linked to above).
No, it won't make your webpage suddenly visible. It just instructs web crawlers on how to index your site.
http://www.robotstxt.org/
I am using joomla 1.5.23 and want to make the URL SEO friendly.. so for that I have used the joomla component JoomSEF 3.4.0 version for this purpose... by using this I have suceeced to change the URL to derired one of my likings but the links are not working.. For make this links to work do i have change the joomla .Htaccess file...
If there is any other relevant components are there.. then also please suggest.. any kind of suggestion will be greatly appreciated... thanks in advance..
Joomla supports SEO URLs without any third party components.
From the administration menu select Site then Global Configuration. You will see the SEO section on the right hand side. You'll see a warning next to Apache mod_rewrite that reminds you to rename htaccess.txt to .htaccess