submitting sitemap using google-appengine custom domain - google-app-engine

I submitted a sitemap using my custom domain name instead of my appspot domain. It has been a week and I have not been indexed yet. I have over 2000 pages, so I am not sure if this is normal or not. I wanted to make sure that I was not supposed to send my appspot domain instead Does anybody know? Thank you,

You can use any domain you want - Google Search is distinct from Google App Engine. All you can do is wait to be indexed.

Related

How do I use my Google App with my a custom domain?

I've looked at previous questions enter link description here, but they use the GSuite Administrator to make changes, while my app uses GCloud. The domain registrar is separate since Google domains don't work in my country.
I mainly followed this guide to setting up my Zones and updating the name servers. I've configured the
https://cloud.google.com/dns/docs/update-name-servers
The question I linked to earlier recommended setting up a www. subdomain, but it used Authenticator. I'm not sure how to do this in a zone. I set up all the records properly in my domain registrar.
Here are the settings:
When I load the site itself (There's no actual HTTP response code):
And when I try the www. subdomain
I'm sure there's a step I'm missing, but this is my first site with GCloud. So I'm not very familiar with the process.
I think where is your missing step.
When you ask Google to use your domain, Google will expose HTTPS endpoint. HTTPS requires a certificate, and Google will generate it for you. However, before doing this, Google has to be sure that the domain belong to you.
You have to prove to google that you own your domain. For this, go to this page, log in and add a property (your website URL). Follow the instruction and be sure that your property has been validated.
Then, wait some minutes (hours?) the time that the certificates are generated and deployed.

Google App Engine specific headers (like X-AppEngine-City) do not work properly for custom domains

I have a google app engine instance running for a custom domain. When I hit the *.appspot.com url I get proper values for headers like X-AppEngine-City, X-AppEngine-Region, X-AppEngine-CityLatLong etc. But when I hit the custom domain url, I get only ? in all the above mentioned headers.
I think since google doesn't send the UserAgent IP to the GAE instance, the instance is not able to determine proper values for the header. Any clue in fixing this issue will be very helpful
Are you mapping your domain straight to the Google IP ranges/CNAME for AppEngine or do you have some sort of proxy such as CloudFlare infront of it.
If your domain name maps straight to AppEngine, I see no reason for those headers not to be set. (I think that around a year ago I used them on a custom domain myself to determine the rough user location in AppEngine.)

Adding custom domain to google app engine

I am a newbie to google compute engine, I looked at various tutorials and could add a custom domain to app engine. I added a sub domain as advised in the tutorial http://demo.appostrophi.com/ [http://demo.appostrophi.com/][1]. I want my URL to be www.appostrophi.com/ but it's showing a blank screen. What could I have possibly done wrong.
I have added the resource names as suggested by google with my domain registrar.
Please advice.
Thanks in advance
Your DNS registration appears incorrect (or didn't yet have time to propagate properly):
Firefox can’t find the server at www.appostrophi.com.
and
Firefox can’t find the server at appostrophi.com.
The document you mentioned is not the proper procedure to register a domain and/or a subdomain to a GAE app. See Adding a custom domain for your application.

appspot.com url shows up in google search results instead of custom domain name

I have set up http://www.footballverdict.com and it's hosted on Google App Engine. Everything works fine. You can visit the custom domain without problems. For some reason when I do a search on Google for "football verdict", the results show startorsit.appspot.com/ask and startorsit.appspot.com/about. There is no footballverdict.com in sight for the main site! It's been at least two months since I hooked up the custom domain. The blog sub-domain does show up in the search results, but that's because it's not hosted on Google App Engine.
Does anyone know how to get the custom domain into the search results and remove the appspot.com sub-domain?
The easiest way to handle this is to have your app detect if it's being requested on appspot.com, and if it is, send a 301 to your canonical domain. Search engines will pick up on this and start listing your canonical site instead.
The answer? Canonical URLs.
Google Webmaster Tools has a great little blurb about it here, and Yoast has another one here.
I hope this gets you pointed in a good direction.
Best of Luck! ~Isaac
Are you using google webmaster? I think this might help. http://www.google.com/support/webmasters/bin/answer.py?answer=83106
It will still take some time for the updates to get into google tho(up to 180 days).

How are people using Google App-Engine apps with their own domains?

I've been fooling around with the Google App Engine for a few days and I have a little hobby application that I want to write and deploy.
However I'd like to set it up so that users are not directly accessing the app via appspot.com.
Is hosting it through Google Apps and then pointing it at my own domain the only way to go? I looked at that a little bit and it seemed like a pain to implement but maybe I'm just missing something.
My other thought was to write the app-engine piece as a more generic web-service.
Then I could have the user-facing piece be hosted anywhere, written in any language, and have it query the appspot.com url.
Anyone have any luck with the web-service approach?
The reason Google Apps is required is because you need somewhere to a) verify you own the domain (otherwise, you might point it at app engine, then I might hijack it by adding it to my account) and b) set up domain mappings (which subdomains point to which of your appengine apps).
Since this stuff already exists in Apps, it seems silly to duplicate it in AppEngine.
As has been pointed out, it doesn't cost anything, and you do not need to "move" anything to Google. You simple created a cname record with a random name to verify you own the domain, and a cname for the subdomain you wish to point at App Engine. This only takes a few minutes, and once it's done, it's done forever.
Note: If you host your site elsewhere and use webservices, you need to scale the site/frontend. If you host on app engine, you get this for free :-)
I wrote an article on my blog about redirecting *.appspot.com domains to your custom domain to keep your branding:
http://blog.dantup.com/2009/12/redirecting-requests-from-appid-appspot-com-to-a-custom-domain
To do this, I believe you need to be using Google Apps and have a custom domain setup for Google Apps. Then, you deploy your app into your Google Apps domain.
Here is google's official instructions on how to do that:
http://code.google.com/appengine/docs/domain.html
I have used this process for a couple of sites and it is easy and painless, provided you have control on the DNS records for your domain (you should).
OK, we're now at the end of 2017 and things are a lot different regarding App Engine and custom domains. It's easy now!
Go to the app engine dashboard for your app and choose Settings, then go to the Custom Domains tab. From there, choose Add custom domain.
The tricky part is that Google needs to verify that you control the domain, so they ask you to put a TXT record in the DNS for your domain. Once you do that and Google it, you become "verified" as the owner of the domain.
After that, Google will give you a bunch of A and AAAA (for IP6) records to put in your DNS. Once you've done that, you should be good to go.
It can be easily done using request.getRequestURI() method. If the URL doesn't include your domain, just redirect it to the desired URL using
resp.sendRedirect("<your domain>")
Otherwise load a error page using
request.getRequestDispatcher("<error-page>").forward(request, response);

Resources