I have a site in meteor with Iron:router. Google thinks that my site has several #! urls that are valid and is displaying them in our results (simply urls that end #!). Iron Router is routing all of these to '/' How do I get it to not do so?
Related
I have a Vue application as a WP plugin, and currently I am migrating it to SPA using Vue router, history mode is used in Vue router, so I will need a redirect from Apache for every route that doesnt exists anymore. What is the way of doing this without reload if user types url in browser and how to redirect that request that to do routing on frontend side without killing current vue instance and reloading whole page, is that even possible with wordpress. Thanks in advance!
I was trying some virtual host configuration and setting fallback resource but without any success.
I have some pages that are /hello.html and should not be changed and others that are /hello, and /hello/. In real life are a bit different, but I would like to don't redirect from /hello to /hello/ or viceversa. Each url is very specific and should not be changed. I was wondering if this feature can be disabled in next.js somehow.
I have a custom server and middleware if any code needs to go there..
Looking for some help with using Wordpress behind a reverse proxy. Got two issues.
The setup is like this.
We host the Wordpress site at: www.myblog.com
The Wordpress version is 5.6.4.
The client reverse proxies the site with IIS at: www.ourdomain.com/blog/
Trailing Slashes
Wordpress will redirect requests from it's root. So if a page request is missing a trailing slash, it will 404. So for example:
Request: https://www.ourdomain.com/blog/myarticle
Redirects to: https://www.ourdomain.com/myarticle which is a 404. It should stay at: https://www.ourdomain.com/blog/myarticle.
It currently only works with a trailing slash.
Indexing for Search Engines
What is the best way to prevent search engines from indexing the site at: www.myblog.com but still allow indexing at:
www.ourdomain.com/blog/
In Wordpress we created some pages like
website.com/page-1/
website.com/page-1/subpage-1/
website.com/page-1/subpage-2/
website.com/page-2/
etc. etc.
Now on the FTP we also created a map called 'page-1'. This map only contains another folder called 'app' (so we have website.com/page-1/app).
Now some visits are getting a 403 error on 'website.com/page-1' because the server does not route the traffic to Wordpress but to the -almost empty- folder on the FTP called 'page-1'. Most browsers do fine, SEO checkers and some proxy's do not route to the Wordpress page.
Can I resolve this issue so that visitors are always getting to the Wordpress page when visiting 'website.com/page-1'?
When I delete the folder called 'page-1' the issue is resolved. Too bad I need this folder because an emailing went out with this specific URL.
I've managed to setup a reverse proxy of my heroku app with the following in config.ru
require ::File.expand_path('../config/environment', __FILE__)
use Rack::ReverseProxy do
reverse_proxy /^\/blog(.*)$/, 'http://blog.domain.com$1', opts={:preserve_host => true}
end
run Appname::Application
This allows my heroku app to run at domain.com and have domain.com/blog appear as the URL while the wordpress site is being served blog.domain.com. Great so far.
The wordpress site gets served properly when going to domain.com/blog, however when I go to any deeper page like an individual post wordpress throws an error. I was using permalinks with the date and title in the URL of the form: domian.com/blog/2012/07/a-great-blog-post - Worpress now seems to not like this. When I switched the links back to the form domain.com/blog/?p=4 the page gets served successfully.
It seems like it doesn't handle and sort of trailing slashes after the inial domain.com/blog properly. What I find strange is domain.com/blog/wp-admin (and the entire WP admin app) works without any hiccups.
Can anyone see any glaring issues why the pages/post with multiple slashes '/' might be causing problems?
Thanks in advance!
Well I found a solution, for whatever reason in the WP settings for the permalink, it didn't like any of the default options except for the form where it can retrieve the post by id. (http://www.domain.com/blog/?p=123)
For SEO purposes I wanted the title of the post to be in the URL. So I entered in the custom structure field:
/index.php/%postname%/
It seems like it was requiring index.php for wordpress to handle the routing properly.