Test your website to see if it’s mobile ready

Google’s official mobile friendly website tester:


Google apps smtp email and relay settings

from: https://support.google.com/a/answer/176600?hl=en

Google Apps SMTP settings to send mail from a printer, scanner, or app

You can set up your on-premises multifunction printer, scanner, fax, or application to send email through Google Apps. The three available options are: SMTP relay service, Gmail SMTP server and Restricted Gmail SMTP server.

For details about configuring your device or application to send SMTP messages, refer to its documentation. Google Support cannot assist with the configuration settings.

  1. SMTP relay service – used to send mail from your organization by authenticating with the IP address(s). You can send messages to anyone inside or outside of your domain.
  2. Gmail SMTP server – requires authentication with your Gmail/Google Apps account and password. Messages can be sent to anyone inside or outside of your domain.
  3. Restricted Gmail SMTP server – does not require authentication, and you will be restricted to send messages to Gmail or Google Apps users only.

The table below will help you decide which one of these options will best meet your needs:

Option Google Apps SMTP relay (recommended) Gmail SMTP server Restricted Gmail SMTP server
FQDN of SMTP Service smtp-relay.gmail.com smtp.gmail.com aspmx.l.google.com
Configuration requirements Port 25, 465, or 587
SSL/TLS optional.
One or more static IP addresses are required.
Port 465 (SSL required)
Port 587 (TLS required)
Dynamic IPs allowed
Port 25
TLS not required
Dynamic IPs allowed
Mail can only be sent to Gmail or Google Apps users
Requires authentication IP address provides authentication. Your full Gmail or Google Apps email address required for authentication No.
Bypasses anti-spam No. Suspicious emails may be filtered. No. Suspicious emails may be filtered. No. Suspicious emails may be filtered.
Sending Limits Limits for registered Google Apps users.
A registered user cannot relay messages to more than 10,000 recipients per day.
For full SMTP relay limits please see Sending limits for the SMTP relay service.
2000 Messages per day. See Sending limits for more detailed information. Per user receiving limits will apply.

You can use the SMTP relay service in the Google Admin console to relay mail from your device or application. This is possible once you add your network IP range to the SMTP relay service. You will need to configure your device to connect to smtp-relay.gmail.com on ports 25 or 465, 587. For more details about using this setting, see SMTP relay service setting.

Gmail SMTP Server could also be used to relay messages from your device or application. You can connect to Gmail mail servers using SMTP, SSL/TLS. If you connect using SMTP, you can only send mail to Gmail or Google Apps users; if you connect using SSL/TLS, you can send mail to anyone.

If your device or application supports SSL – connect to smtp.gmail.com on port 465.

To connect with SSL, you need to provide a Google username and password for authentication. Ensure that the username you use has cleared the CAPTCHA word verification test that appears when the user first logs in. We also recommend ensuring that the account has a secure password.

If your device or application does not support SSL – connect to aspmx.l.google.com on port 25.

You must configure an SPF record for your domain with the IP address of the device or application to ensure that recipients do not reject mail sent from it. You must also add this IP address to the Email Whitelist box in your Google Admin console. For example, if your sending device sends from, add that address to your SPF record without removing the Google Apps mail servers from the record: v=spf1 ip4: include:_spf.google.com ~all

Improve your Google Places business listings

Don’t do these 9 things:

from: http://searchengineland.com/9-common-ways-to-bork-your-local-rankings-in-google-99336


Google Apps – reset a users password

from: http://support.google.com/a/bin/answer.py?hl=en&answer=33319&topic=14588&ctx=topic

You can always reset the password for a user on your domain. This is helpful when:

  • A user forgets his or her password
  • A user’s account is compromised (security concerns)

To reset a user’s password:

    1. Sign in to the Google Apps administrator control panel.

      The URL is https://www.google.com/a/cpanel/primary-domain-name, where primary-domain-name is the domain name you used to sign up for Google Apps.


    1. Find the user account. You can either search or browse:
      • Search: Enter the user name in the search box at the top of the Google Apps control panel, then click Search accounts.
      • Browse: Click the Organization & users tab from the top menu. Select an organization from the organizational structure on the left.


  1. Click the row for the user account to display the user information page.
  2. Click Change password.
  3. Enter the user’s new password in the Password: field, and then enter it again in the Re-enter Password: field to confirm the change.

    When you enter the password, the Password strength field below the text boxes evaluates the security level of the password. Click the link if you want tips for creating strong passwords. Google requires a password that’s at least eight characters, especially for optimal use with IMAP or POP.

  4. Specify whether you want to force the user to change the password the next time he or she signs in.

    Select the Require a change of password in the next sign in check box to require the user to create a new password.

  5. Click Save Changes along the bottom.

Once you’ve reset a password, be sure to provide the user with new login information.

Google Penguin update – same anchor text now hurts website SEO

If you have the same anchor text in your footer links on all the websites that you create this can now hurt your website SEO. This happened to edublogs, they had to remove more than 10,000 footer links.

Another way to avoid the Penguin update penalty is by making your anchor text footer links nofollow.

Google Them 2013

In the new year 2013, GoogleThem.com has been providing google tips and tricks and more since November 2007, starting with an early version of WordPress MU (2.7) and now running WordPress 3.5!

The Hardware is freshly upgraded for the new year to a dedicated Xeon X3430 8 core, 32 Gigs of RAM, 1TB hard disk server.

Want to see all the data on you that google has stored?


Login with your appropriate google account and here is your privacy information that is available to google and to you.

Cannot see new version of website – updates not showing – sticky cache

1) Control-R (or Command-R) – Control – F5 does the same thing on Windows

2) Go through your options and empty the cache manually

3) Try another browser

Users do not normally notice the old website hasn’t changed because they are not talking to the developers and wouldn’t know when the website really has been updated. This happens all the time.

Most likely you have a “sticky cache” on your computer.

Here’s the trick: Whether you get to http://yourwebsite.com by clicking this link, or by going through google, once you see http://yourwebsite.com in the top line of Internet Explorer, Firefox or Chrome (The URL or Location bar), do a hard refresh.

Hard refresh is done when you are supposed to be seeing the new webpage that you are having trouble with, and reaching out to your keyboard, while holding the “control” key, tap and letup on the “r” key, then let go of the “control” key. (Ctrl-r)

This dumps the old cached page that is sitting on your computer and tells it to go load the new one from the internet.

This insures that you are seeing the latest changes to your website.

The “sticky cache” issue is common when developing new websites. Usually people don’t notice changed pages so much because they don’t know the page should have changed. It happens more often than people realize.

Note: If you have an alternate web browser installed that you haven’t used lately, just view the website in it, you should see the latest version automatically, since it’s not been “cached” lately. Browsers do not share each other’s cache.


If you have a really sticky cache:

Log out of WordPress, clear your browser cache, quit and restart the browser and try again. If that does not work, there may be a caching proxy or network cache somewhere between you and your host. You may need to wait for a few hours until this cache expires.


Note: CSS changes can cause a really sticky cache when background images are changed, they tend not to update unless you clear your cache.

SOPA has been stopped

On the 18th, this website joined google, wikipedia and many, many, many others in a blackout in protest of SOPA and PIPA.

We won this one!

Today on January 20th, 2012 it was announced that the bills are being dropped.

Think we’ll fly the ribbon on the upper right corner of the website for some time more to appreciate that change and direction can come from internet collaboration.

Thank you, one and all who joined in on the protest to keep the internet open.

This is our lifeblood and prosperity.

Does google still count page visits or hit in analytics if the cached version is clicked?

The answer to this is sitting right next to another interesting fact from the google forums, how does google count page hits?

From: http://www.google.com/support/forum/p/Google%20Analytics/thread?tid=11df99a64a48364c&hl=en

“Caching: Google Analytics directly calls Google’s servers each time a page is visited, even if the page has been cached. Other analytics solutions may not record an additional visit if the page is pulled from a user’s or server’s cache.”