1. Barb Emerson

    Excellent. As I work to move my customers toward the easiest method of Getting Stuff Done, this is a satisfying step forward.


  2. Claire Brotherton

    This definitely looks like a good feature and will speed up a lot of people’s workflow.

    I’ve been frustrated before by the extra tags generated by pasting in content from Google Docs – good to know that problem’s been solved.

    Will be interested to know how well it works as part of Jetpack on self-hosted sites. Which host gave you problems?


  3. N

    Does this work only ion “wordpress.com” or other sites with wordpress installed?


    • Jeff Chandler

      WordPress.com and Jetpack-connected sites.


      • Justin Lewis

        I haven’t been able to get it to connect on my Jetpack-connected site. When I go to authorize it I am taken to my login page. When I log in with the correct credentials I see the following message:

        Someone may be trying to trick you into giving them access to your site. Or it could be you just encountered a bug :). Either way, please close this window.


        • Jeremy Herve

          Hi! I work on the Jetpack team, and I’d be happy to help you figure this out!

          Can you please use Jetpack’s Debugger module to send us some more information about your site?

          Go to the Jetpack page in your dashboard.
          Click on the Debug link appearing at the bottom of the page.
          Click the link that says “click here to contact Jetpack support.”
          Fill in the description box and your name and email address.
          Click the “Contact Support” button to send us the debug results privately. It’s best not to post this information here, as it contains private details about your site.



        • Tom

          Had the same problem, and resolved it. In my case, my (self-hosted) WordPress site (using Jetpack) is https:// not http://. I had a few lines in my .htaccess file that FORCE https (to prevent search engines from indexing both):

          RewriteEngine On
          RewriteCond %{HTTPS} off
          RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

          I removed those lines, and presto – Authorization worked as intended.

          After I was authorized, I added them back, and the add-on works perfectly. It was apparently only a problem during the authorization step.

          Hope that helps!


  4. Garikai Dzoma

    I feel like I have been waiting for this all my life. While almost all of our authors know how to use Google Docs, WordPress’s default editor requires some learning for them and even now they still make mistakes. And there are times when one has to go to the text editor for example to tweak lists. They get lost.


  5. Patrick Steil

    This will be a great tool for our church website clients! Anything to make their lives easier and quicker to get their content on the website is great!


  6. Birgit Pauli-Haack

    This new Chrome extension is great news for our team. We co-author heavily in Google Docs. We too had trouble connecting with Jetpack on one site, and it seems when you change over from HTTP to HTTPShttps, some of the Jetpack features, among them the Google Doc Extension doesn’t work, without disconnecting on both sides. After disconnecting the site from my WordPress.com account and disconnecting the Jetpack instance on the site, and then reconnecting, would allow a proper authentication of the Google Docs.


  7. Will Wilson

    I’ll be happy to give this a go when it works…….

    Several issues with trying to authenticate.


  8. Bren Pace

    This is absolutely fabulous news! I’m so excited to get started with it and use on 4 of my sites! Thanks for sharing this!



  9. Vitor Madeira

    Can’t wait to try it out… Thank you Sarah.


  10. Angela

    Will the original remain in Google docs after posting to the WordPress site?


Comments are closed.

%d bloggers like this: