Welcome to the Q&A Forum

Hi Robin, Nigel has offered some good advice here - the one thing I would also add is that you may want to set up mobile switchboard tags to make it clear to Google that the desktop version is the canonical version for PCs and the mobile version is canonical for mobile. See more info here: https://developers.google.com/search/mobile-sites/mobile-seo/separate-urls#annotations-for-desktop-and-mobile-urls

Does urls with numbers accepted by various SEO submission sites? If not, which sites are mainly not accepting? Can you kindly list a few if possible?

Hi Robin, There's no indication Google is having any trouble picking up the separate URLs and their associated Titles and Descriptions properly - a site: search for your domain returns all pages I'm able to find manually, and each page has a unique and accurate Title and Description snippet. ReactJS is one of the most commonly used JS platforms, with a lot of momentum in the development community especially on high-traffic sites, and Google has innovated their crawl tech to include JS-support (they crawl with a headless version of Google Chrome) to adapt to this platform. "View Source" is no longer valid for interpreting page code as Google will render it - they crawl with JS support, so JS interactions and modifications of source code are visible to Google. Using "Inspect Element" in Chrome shows a more accurate representation of what Google can crawl/render. In short: I see no negatives for SEO here, and I expect at this point your analytics and Search Console data will show that your pages are indexed and eligible for traffic (potentially already getting traffic) from Google. Best, Mike

Hello there! Sam from Moz's Help Team here! If the only change made to your site's URL is that it is now https instead of http, our tool should start crawling the https pages without needing to create a new Campaign. You can check to make sure that the https pages are being crawled by heading to your All Crawled Pages section of your Site Crawl and filter by "https://" in the search bar. This can be a quick way to make sure we're capturing that update! If you email us at help@moz.com with the campaign name, we'll be happy to check for you! In the case of a URL switch, especially an HTTP to an HTTPS, remember that it is normal to see a bit of a drop in some of your stats just after the move. We have a blog post about migrating to HTTPS: https://moz.com/blog/seo-tips-https-ssl There are also some great Q&A threads about the potential impact: https://moz.com/community/q/our-homepage-url-has-been-301-d-to-the-new-https-version-as-our-md-wanted-us-to-have-the-secure-protocol https://moz.com/community/q/will-switching-to-https-lower-my-domain-authority In terms of indexing, this is something I would recommend checking in your Google Search Console. Google has a great guide here: https://support.google.com/webmasters/answer/6033049?hl=en Hope that helps provide some insight! If there's anything else you need, just let me know — I'm always here if you need any help!

Everything we made perfect even our google plus logo also. Still it's not picking from those sources.

Where the issue becomes more complex, is if you add CloudFlare to your site for DDoS protection, to serve up from closer towers, etc. Many sites who want to load faster or avoid attack are doing so. We have thus incurred a redirect issue to work through and it takes some technical expertise. Because CloudFlare is a third party for SSL certificates in many hosting packages, this seems to catch many off-guard and wondering what went wrong. If helpful, we have had greater success buying our own CloudFlare service versus letting a hosting provider be an affiliate service for our SSL.