How to count the number of hits to my redirected Google domain - google-domain-api

I have a Google domain (let's say mobiusdickus.com) that I simply use to redirect to another website to which I do not have administrative rights (let's say wikipedia.org). How can I count the number of hits to mobiusdickus.com?
Edit: I found a work around by instead forwarding the website first through Google URL shortener, which has built-in analytics :)

Related

Restrict all access to S3 static website except from our Elastic Beanstalk website

We have an Elastic Beanstalk instance that serves our PHP website (example.com). We just added an S3 bucket which serves a different static website (static.com).
The EB website (example.com) requires specific credentials which are supplied to the end-user for logging in. We would like to have the S3 website (static.com) only viewable to the logged-in users of the EB website (example.com) .
Use Cases:
A user is logged into “example.com”. Within the site there would be links to the files on “static.com”. Clicking on these links would take the user to the files on “static.com” and they could navigate around that site.
Someone has a URL to a page on “static.com”. Maybe someone shared that URL with them (that is expected behavior). When they attempt to load that URL in a browser, they are redirected to the login screen of “example.com” to login.
What is the best, and easiest, way to accomplish this? Cookies, Cloudfront, Lamda functions? “Signed URLs” sounded like a possible avenue, but the URLs cannot change over time. This is a requirement in case users do share the URLs (which is expected and ok). Example: Hey Johnny, check out the information at "static.com/docs/widget_1.html"
If you have private content, CloudFront signed URLs are the right choice to generate unique URLs for authenticated users of your application for a limited time. Each time a user loads a page, you generate new short-lived URLs.
If you'd like to enable someone to share links, one option is to provide users with a share option in your application that generates a SignedURL with a longer TTL of a fixed amount (e.g., 3 days) for sharing. Or enables the user to select the length of time the shareable link should be valid, with a maximum allowed time period of x hours/days. If the link expires, they can generate a new one in the application.

How to forward my domain registered with AWS Route53 to Google My Business?

My domain: fishercoder.com is registered with AWS Route53.
Now I'd like to configure Google My Business to use this domain.
I searched on Google's doc and found that they do offer clear instructions on how to purchase a new domain through them, for third-party domain they listed instructions for GoDaddy, eNom and Network Solutions, but none for AWS Route53.
I thought it might be similar, so I tried to simulate what I can do on AWS Route 53 console, but didn't find any luck.
Any could share any ideas how to achieve this?
More details:
Right now, when people search "fisher coder", this page shows up: https://ibb.co/pRWjRc9, and if they click Website, it'll take them to the default Google My Business website which is not what I desired, I'd like to change it to point to my own domain: fishercoder.com
Thanks!
You can do it but it’s not a pretty solution. Not only that but a Google My Business Site (I assume this is what you mean) is so basic it’s not a good website replacement at all. It’s a good free option to set up because it’s free but other than that, it’s meant to keep people in Google, not to help you. You can only map custom domain buy from from business sites option given there.
Here’s how you do it:
Buy a domain wherever you prefer (I like Namecheap but Google Domains is also a good option).
Forward the domain to the Google Sites URL (many registrars will allow you to do this for free).
That’s it!
It’s not a pretty solution nor ideal because the URL of the Google Site will still be the original URL and they won’t stay on your custom domain at all.
So, simple description: if someone types in http://customdomain.com they will get forwarded to your Google URL and remain on that URL. It essentially just forwards to your Google Site, that’s it.
In AWS routes you will get option to forward domain. https://aws.amazon.com/premiumsupport/knowledge-center/redirect-domain-route-53/
This all information based on own experiment and study based on below link
Reference info : https://www.quora.com/How-can-I-attach-a-custom-domain-to-a-Google-Sites-website

Google Cloud Login Widget like Facebook

I am creating a solution for my customers. This solution will allow them to check SEO parameters of their websites. This requires a script to be executed on Linux instance. However, I want them to use their own Google Account. The work flow should look like this:
Let's my website is www.example.com.
Customers open www.example.com on their browser
On my home page there is widget that allows them to login into their Google Account
Once they have logged in - I should be able to use their security tokens to launch an Linux instance
Then my script for grabbing SEO parameters would run on their Linux instance.
Limitations:
I know it can be done using their API keys / secret but I want a widget much like FaceBook widget (that allows particular APP to run)
I don't want to burn my cash running the script for their websites.
Is there any that can be done like this?
I am also open to alternatives as long as I don't spent money on compute.

Get Github Pages Site found in Google Search Results

I have a site built with Jekyll Now on GitHub and I want it to appear in a google search. If I just google my GitHub username followed by 'GitHub' and 'io', it does not find my site. How do I get google to find my site in a google search?
You have to create a Google Search Console account and add your page, then typically you just drop a "marker" file in the root (Search Console generates this) so that Google can confirm you really own the page.
Google Search Console
Instructions
(Since the instructions are long and have many links to sub-steps, I'm only providing the link.)
Also, if you're going to use a registered domain name, set that up before you register the site for search.
(Edit: Technically you don't have to do this, sooner or later Google will find you... but this will give your content a much higher-quality score.)
It can take a few days before the site is indexed by search engines. Google for google index site and you will find quite a lot of information about the process and how it can be speed up.
Generally, google finds all website and index them. Sometimes, it's takes time to crawl the new website.
But, you can do this thing manually by following these steps:
Go to Google search
Add the website as your property
Then, verify your property that you're the owner of this.

Find and Replace with correct URL

There are region specific URLs for various websites like google.co.in or google.co.uk for google.com, So for the major sites like google, facebook, linkedin, I want to replace their region specific URLs with all region URL.
For example for google, it should be redirected to https://www.google.com/webhp?pws=0&gl=us&gws_rd=cr.
The solution which I was trying:
1) Take the part of URL google.co.in(using regex) and replace it with google.com (using re:replace)
2) For storing of initial and replacement URL, I'm thinking to use orddict, where {key,value}={"...//google.co.region/...","...//google.com/..."}, region can be in or uk or any other, so how to take that region into consideration if I'm using orddict as keystore ?
But I'm not sure how to actually implement this in erlang or whether my proposed solution will work properly ?
I'm doing this for my messenger app, so whenever user enters URL, it doesn't show preview of URL where my server is located, instead atleast show it in english.(as per now ,for facebook, my app shows preview in russian)
There's built-in regex module in Erlang: http://erlang.org/doc/man/re.html
As for your solution, it really feels like a crutch for functionality better achieved with smart networking. Or you can try making requests for a preview on client's side, not server, for example.