Google search console: inspect the previous domain after performing 301 redirection

After redirecting to a new domain

I tried to inspect the URL of the previous domain of your webmaster and obtained this information

The URL is not in Google This page is not in the index, but not by
a mistake. See the details below to find out why it was not indexed. To learn
plus

enter the description of the image here

If so, then Why do I keep losing my rank in Google search?

Also, I would like to know what is the difference between the Reference page Y Canonical declared by the user?

vhost: 301 redirect for the "/ use" page while the webalizer is installed

I moved my site to another hosting provider and it is using webalizer. My site has a page called /usage.

While testing I discovered the page https://example.com/usage/ generates the 403 Forbidden error due to this webalizer.conf:

#
# This configuration file maps the webalizer log analysis
# results (generated daily) into the URL space.  By default
# these results are only accessible from the local host.
#
Alias /usage /var/www/usage


   # Alternative e.g. "Require ip 192.168.10"
   Require local

OK, I changed the name usage to some-usage and created a 301 redirect but apparently the configuration file has a higher priority.

My questions):
Can I be more specific in webalizer.conf and tell Apache to ignore /usage when that is in the https://example.com/usage/ context or how can I configure redirection 301 to work.

Personally, I would prefer the solution where Apache ignores /usage in the https://example.com/usage context.

ssl – 301 Redirect Loop www a non-www – Nginx + Apache2

Thanks for any help. I am not a server, but I am dealing with a server at the moment. I have a site that is in a redirect loop from www to non www. I am using a DigitalOcean Droplet with Ubuntu and Nginx for SSL. I originally had problems for SSL to work and I created a configuration based on this post in StackExchange: WordPress redirect loop in nginx + apache reverse proxy. The main difference I had made was to use a 302 redirect in the last block of the server. However, someone told me to change it to 301 and now I'm getting the loop from www to no www. Below is my configuration file.

server {
        server_name .mysite.com;
        root /var/www/html;

        # Add index.php to the list if you are using PHP
        index index.php index.html;

        gzip on;
        gzip_types application/javascript image/* text/css;
        gunzip on;

        location ~.(js|css|png|jpg|jpeg) {
                try_files $uri $uri/ =404;
        }

        location / {
                try_files $uri @apache;
        }

        location ~(^?)*/$ { # proxy directories
                proxy_set_header X-Real-IP  $remote_addr;
                proxy_set_header X-Forwarded-For $remote_addr;
                proxy_set_header X-Forwarded-Host $host;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header Host $host;
                proxy_pass http://127.0.0.1:8080;
        }

        location ~ .php$ { # serve php files
                proxy_set_header X-Real-IP  $remote_addr;
                proxy_set_header X-Forwarded-For $remote_addr;
                proxy_set_header X-Forwarded-Host $host;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header Host $host;
                proxy_pass http://127.0.0.1:8080;
        }

        location @apache { # used by location /
                proxy_set_header X-Real-IP  $remote_addr;
                proxy_set_header X-Forwarded-For $remote_addr;
                proxy_set_header X-Forwarded-Host $host;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header Host $host;
                proxy_pass http://127.0.0.1:8080;
        }


        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        location ~ /.ht {
                deny all;
        }

        listen (::):443 ssl ipv6only=on;
        listen 443 ssl;
        ssl_certificate /etc/letsencrypt/live/mysite.com/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/mysite.com/privkey.pem;
        include /etc/letsencrypt/options-ssl-nginx.conf;
        ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;

}

server {
    listen 80;
    server_name _;
    return 301 https://$host$request_uri;
}

Note: changing 301 back to 302 did not solve the problem.

Please help, thanks!

Edit: I have also confirmed that there are no references to www.mysite.com in the database. I have used WP-CLI to find some. And the home and site URLs have always been without www.

seo: URL modified for a page indexed by Googlebot. It will redirect 301 of the previous URL to the new one. But what to do with my Sitemap?

I am planning to change a URL for one of the pages of my site.

Example:

Since: https://www.example.com/old-post-slug

TO: https://www.example.com/new-post-slug

The fact is that Google has already indexed the old URL: https://www.example.com/old-post-slug

And from these DOC, we see that to avoid losing the page ranking we must respond with a 301 - Moved permanently from the previous URL that points to the new URL.

https://support.google.com/webmasters/answer/6033049?hl=en

enter the description of the image here

QUESTION

I understand that I should redirect (301) from the previous URL to the new one. Then, when Google crawls again, you'll see that change. But what should be on my Sitemap? The previous or new URL? Or both?

I tend to think that it would be better to keep only the new URL in my Sitemap. But what happens if Google crawls the new URL before seeing the redirection of the previous one? Wouldn't the new page URL start as a new page (from the Google index perspective) with zero ranking points? How does Googlebot handle that? What is the recommended practice?

dns – Troubleshooting redirects of Cloudflare 301

My client has a URL that they want to redirect completely to another site (301 redirect). This domain is purchased and managed through GoDaddy (unfortunately). After configuring the redirection, I received problems because the URL did not have an SSL certificate installed. GoDaddy charges $ 80 / year for SSL certificates. I tried to avoid this by routing traffic through Cloudflare, but my records and page rule settings don't seem to be doing anything.

Anyone know how to do this correctly?

Redirection 301: Marketing friendly URL

A client has a very long scripted domain. I can not do anything about it. Although we are also looking for new domains, if that is a better solution.

You need a friendly URL for marketing, to print on cards and brochures.
The target audience is over 50 years old. A friendly URL will facilitate access to the website.

What are the implications for a friendly URL that redirects to the website?
Can it damage SEO?

Outlook web application: Exchange 2010-2016 coexistence: why does OWA perform a 301 redirect before logging in?

I have an Active Directory domain. We have two local mail servers: one that runs Exchange 2010 (exchange2010.example.com) and another that runs Exchange 2016 (exchange2016.example.com). My goal is to migrate from 2010 to 2016, but have them live together during the transition.

We have a firewall (pfSense) and allow access to OWA using NAT. I have a NAT rule that points to the Exchange 2010 server and one that points to Exchange 2016. From the outside, the IP for both servers looks the same (since both run from the same Internet connection), but there are two CNAME entries in external DNS, and NAT forwards two different ports.

Internally, everything works. If I go to https://exchange2016.example.com/owa I get the OWA 2016 login page. I can login. If the mailbox is in Exchange 2010, the OWA proxies and I get the OWA of 2010. Otherwise, I get the 2016 interface.

Externally, I have the following URLs: https://exchange2010.example.com/owa and https://exchange2016.example.com:8443/owa. This is where things get weird.

Let's say I visit https://exchange2016.example.com:8443/owa. I can see in the firewall logs that the client connects to the Exchange 2016 server. But then there is an immediate 301 redirect to exchange2010.example.com, and I get the OWA login page for Exchange 2010, not Exchange 2016. This happens BEFORE you log in, so OWA doesn't know anything about where mailboxes live. The domain name (exchange2016.example.com) remains the same, but I lose the forward port (8443) in the URL.

I can see that there is a redirection in the firewall and IIS logs, but I don't know what is causing it. I think that the external URIs in my virtual directories are configured correctly.

Does anyone know what could be happening here? Where should I look for troubleshooting information? I don't think the problem is the port forward, but I don't know how I would say it.

What is the best way to perform 4 million URL redirects 301 jpeg?

I certainly don't want to list 4 million redirects in my nginx configuration files … what is the best practice with a lot of redirects like this? They would be permanent and old links live in many historical emails from customers, so I can't count on Google et al to update their indexes over time.

I suppose I need to have a 404 configuration that verifies the requested JPG with an old URL database with its corresponding new URL?

seo – Someone is 301 redirecting penalized websites to my website

Some are doing a negative seo attack on my site 301 redirecting toxic sites to my site, I have researched and nobody online seems to have an answer, I would reject the domain doing the 301 job or I need to reject all links to the 301ed Domain that are subsequently being redirecting? Is there also some way in the htaccess to cause a redirect loop for them?

Effect of redirection 301 for the expiring domain

What happens if an old domain that redirects to a new domain expires? Will you continue redirecting? What is the effect on the search engine ranking?

Thank you