FlowPaper 3.1.2 Release Notes

Monday 23rd October 2017

The points below highlight some of the more noticeable changes this month. Mainly Elements and Zine has been affected by this months changes.

How to update
You typically don’t need to update your converted resources if you’re only interested in behavioural fixes. You can replace the js/ and css/ directory of any existing publication to update.


  • Added support for YouTube’s short url variant (youtu.be) (Desktop Publisher)
  • Added the ability to export invisible text for Zine (Desktop Publisher)
  • Improved rendering for Zine in Firefox (Desktop Publisher)
  • Zine is now able to show the outline of a document when only providing a PDF file (Zine)
  • Improved page loading to avoid pages being interrupted incorrectly on slow network connections (Zine)
  • Improved output rendering quality for two-fold publications in flatten/compressed mode (Desktop Publisher, Zine)
  • It is now possible to define where sections should start when using the Reflowable mode (Desktop Publisher)
  • Its now possible to go into full screen (simulated) in iOS when using Elements (Desktop Publisher)
  • Various improvements to the editing mode for Elements (Desktop Publisher)
  • Improvements to the reflow TOC menu that pops up from the top right corner (Desktop Publisher)
  • Improved font loading for IE / Edge when using flatten/compress (Zine, Desktop Publisher)
  • Zine now updates the #page hash parameter when navigating, making it easier to return to the last read page when returning to the viewer (Zine)
  • Improved bottom margin for Zine when using the viewer without bottom thumb nails (Desktop Publisher)
  • Improved the Elements mode so that fonts won’t need re-conversion when opening existing publications (Desktop Publisher)
  • Fixed an issue where the TOC changes were not being saved when using the Elements viewer after reopening a existing publication (Desktop Publisher)
  • Fixed an issue where the publication title was incorrectly escaped when publication preview was set (Zine)
  • Fixed an issue where some fonts went missing after changing output settings under Zine (Desktop Publisher)
  • Fixed an issue where PDFs using non-embedded standard fonts where texts that had italic were not having their italic set properly (Zine)
  • Fixed an issue where the zine viewer would get 35px padding area at the bottom of the viewer after a resize occurred for some scenarios (Zine)
  • Fixed an issue where uploading to the cloud service failed in some cases where the file got locked by the file system (Desktop Publisher)
  • Fixed an issue where disabling the bottom thumbnails in Zine would render a margin too small in some browsers (Desktop Publisher)
  • Fixed an issue where importing multiple files at the same time would import the files in wrong order in some cases (Desktop Publisher)
  • Fixed an issue where relatively positioned viewers were causing the text to be mispositioned in some cases (Zine)
  • Fixed an issue where soft hyphens were appearing incorrectly in FlowPaper Elements (Desktop Publisher)
  • Fixed an issue where uploading the same publication twice to FlowPaper cloud would fail to refresh the publication (Desktop Publisher)

FlowPaper 3.1.1 Release Notes

Sunday 17th September 2017

This release mainly contains smaller corrections and improvements. We’re getting this release out a little earlier than usual due to iOS 11 being released in the next 48h as we found some optimisations we wanted to include prior to this release. We have seen some issues in iOS 11 related to how background images are being loaded and unloaded in the Safari browser and we have made optimisations accordingly. This was mainly affecting the Zine viewer.


How to update

You don’t need to republish existing publications to update if you’re mainly interested in the adjustments for iOS 11. You can simply replace the existing “FlowPaperViewer.js” file in the js/ directory of any publication or installation you have created with the new version. You can grab the minified version of FlowPaperViewer.js here.



  • Cosmetically improved the 3D page turn effect (Zine)
  • The vertical reflow template will now scroll on devices with larger display width than 500px (Elements)
  • Its now possible to deep link into reflowable vertical publications using the #section hash (Elements)
  • Improved text quality when changing pages in Zine while rendering in 3D mode (Zine)
  • Improved loading speed for WebGL in Zine mode (Zine)
  • Improved height calculation for the bookmarks/outline panel in Zine (Zine)
  • Improved the reflow template so that fixed layout pages are not shown until rescaled (Elements)
  • Improved preview quality for sharing publications on Facebook / Twitter via opengraph (Desktop Publisher)
  • Improved drawing accuracy for the drawing & selection tool (edit mode) (Desktop Publisher)
  • Additional storage can now be purchased from the account/cloud publications page (Web)
  • Improved support for iOS11 (Zine)
  • Added support for Parallax pages (useful for pages with large backgrounds) to the vertical scrolling Reflow mode (Desktop Publisher)
  • Improved the Elements viewer further to avoid flickering in some cases when changing page and images were being loaded from cache (Desktop Publisher)
  • Fixed an issue where the last page got duplicated incorrectly when using Elements after changing some of the settings (Desktop Publisher)
  • Fixed an issue where some standard fonts were not having their bold/italic set properly when using the flatten/compress option in Zine (Desktop Publisher)
  • Fixed an issue where navigating using the hamburger menu with SEO optimizations turned on caused the viewer to freeze in Chrome (Elements)
  • Fixed an issue where fixed layout areas were not being centered properly in iOS (Reflow)
  • Fixed an issue where some standard fonts were not being used properly when using flatten/compress (Zine)
  • Fixed an issue where holding down left/right arrows and not releasing to navigate would cause graphical glitches (Zine)
  • Fixed an issue where some images were not being exported properly in the new reflow template
  • Fixed an issue where vertical/reflowable publications were not using Google Analytics tracking properly (Desktop Publisher)

How to correct the reading order in PDF documents automatically

Thursday 31st August 2017

You may have noticed that the text selection can behave erratic when selecting text in your PDF reader (such as Adobe Reader). This is because text in a PDF document is not necessarily ordered in logical reading order. You can see an example of this behaviour in Figure 1.

Figure 1

So why is this a problem? It’s a problem because of two reasons; firstly, it means that Google will most likely index text in your document in the incorrect order. Sentences are in some cases broken and as a result you may not be getting the search hits you’re after for your content.

The second problem is that people who use screen readers won’t be able to read the documents properly. Text will most likely be read out in the wrong order.


Fixing the reading order automatically

The typical solution when dealing with reading order problems is to use something called PDF tagging. This requires you to go through the entire document and tag each text and mark which text that should follow that text in reading order.

Using machine learning, FlowPaper is able to reconstruct the logical reading order of your documents without any manual tagging work. Single column layouts, multiple column layouts, you name it. FlowPaper does this by analysing the layout of the page very much in similar ways as the human eye is recognising a page and its reading order.


How to fix the reading order of your PDF

Make sure you have the desktop publisher installed. It can be downloaded from our public download page.

Figure 2
  1. Firstly, Start up the desktop publisher and select the “Elements – Slide” viewer in the top right corner as seen  in Figure 2
  2. Make sure the “Improved Accessibility” checkbox is ticked in the “Accessibility & SEO” section
  3. You can now go ahead and import your PDF. Make your desired adjustments to style and click “Publish” in the top.


Verifying the Results

So how can we check that the corrected reading order is correct?

You could let a screen reader read it out if you have one installed. You can also check the text order manually if you know your way around Chrome a little bit.

  1. To use Chrome to check that the elements are in the correct order, open the publication in Chrome using “View Offline Version” from the desktop publisher and open up the Chrome dev tools from the View->Developer->Developer tools menu
  2. What you will see now is all the HTML5 elements that the desktop publisher has created when converting your PDF document. An easy way to check the reading order is just to step through the elements like in the animation below.


Voila! Please let us know if you have any questions regarding reading order or how it can be used in other scenarios!



FlowPaper 3.1.0 Release Notes

Thursday 31st August 2017

We’re pleased to announce our latest release of FlowPaper, featuring a number of enhancements and improvements especially around our Desktop Publisher. Version 3.1.0 will be rolled out during the next 24-48h and will appear in the commercial download archive accordingly.

The main changes in this release can be seen below:

  • Improved the font loading in the vertical reflow template (Reflow)
  • Now displaying source page when hovering over text while in edit mode in reflowable publications (Desktop Publisher)
  • Improved progress information for two-fold publications (Desktop Publisher)
  • Improved the ePub3 output template (Desktop Publisher)
  • Further ePub3 validation improvements for iBook store (Desktop Publisher)
  • The Elements viewer has been further improved to handle scenarios with differently sized pages better (Desktop Publisher)
  • The vertical reflow mode now allows swiping between sections as opposed to scrolling through all sections at once (Desktop Publisher)
  • New page animation added for Zine (“3D, Bend”) (Zine)
  • onCurrentPageChanged events now dispatched in vertical (reflow/fixed layout) mode (Desktop Publisher)
  • Improved shadows in Zine 3D modes (Zine)
  • Its now possible to change email in the account area (Web)
  • Its now possbible to resize images in Adaptive and Reflowable editing mode (Desktop Publisher)
  • Support for opengraph added to Zine to support preview images when sharing on Facebook / Twitter (Zine)
  • Improvements to text clipping (Zine+Adaptive+Reflow)
  • Improved page loading in Zine (Desktop Publisher)
  • Its now possible to hide/show the top bar in vertical reflow mode (Desktop Publisher)
  • Its now possible to change font size on text in Elements publications (Desktop Publisher)
  • Its now possible to change font color on text in Elements publications (Desktop Publisher)
  • Improved performance for the desktop publisher when going into edit mode (Desktop Publisher)
  • Improved sub-pixel rounding accuracy for Safari & iOS in the new reflow template (Desktop Publisher)
  • Its now possible to start drawing into any direction when adding interactive elements (Desktop Publisher)
  • WebGL 3D shadows for touch devices disabled to improve performance in flipping pages on low CPU devices (Zine)
  • The desktop publisher now allows multiple domain names to be entered at the same time for Creative and Creative Team license holders.  Separate the domains with semi colon (;) to generate keys for multiple domains at the same time (Desktop Publisher)
  • Fixed an issue where the reflowable mode would fail on texts that were filled with patterns (Desktop Publisher)
  • Fixed an issue where some image resources were incorrectly cleared when switching from 10 pages to all in Zine (Desktop Publisher)
  • Fixed an issue where links/videos/images added to two fold publications would have them duplicated in certain scenarios (Desktop Publisher)
  • Fixed an issue where two-fold Elements publications were not being adjusted when reopening them (Desktop Publisher)
  • Fixed an issue where unicode characters were incorrectly unescaped in the Zine bookmark list (Desktop Publisher)
  • Fixed an issue where differently sized pages would default to their unadjusted dimensions in some scenarios causing the annotations marks to be mispositioned (Classic)
  • Fixed an issue where the TOC background color wasn’t being set when using Zine in portrait mode (Desktop Publisher)
  • Fixed an issue where the viewer wasn’t navigating to sections properly in vertical reflow mode (Desktop Publisher)
  • Fixed an issue where some fonts were incorrectly repaired as part of the conversion when adding missing spaces (Elements, Desktop Publisher)
  • Fixed an issue where phone numbers were incorrectly detected by Microsoft Edge browsers (Elements, Desktop Publisher)

FlowPaper 3.0.3 Release Notes

Tuesday 1st August 2017

Summer is running at full throttle on the northern hemisphere and so are we down under to get you a new fresh build out as you come back from summer holidays! This release features major updates, particularly to the reflow viewer.

A new reflow template has been added and new supervised and unsupervised machine learning algorithms are in place to help with the reflowing of publications. Following this release, there will be multiple subsequent updates to the reflow functionality where we fine tune and adjust these algorithms in the next few months.



  • Huge overhaul over the reflow functionality with new machine learning algorithms in place for better text and layout analysis (Desktop Publisher)
  • New template using a vertical layout introduced for reflowed publications (Desktop Publisher)
  • Fixed an issue where the bookmarks were not resolved initially causing some of the reflowable documents to not use them correctly (Desktop Publisher)
  • Additional metadata fields added to the EPUB3 export routine (Desktop Publisher)
  • Fixed an issue where Vimeo videos would hide the cover after clicked when used with the maximise setting (Zine)
  • Improved search matching when searching for partial words (Zine, Classic)
  • Zine is now centering the mobile view vertically when no bottom thumbnails are visible to allow space to be better used (Zine)
  • Improved handling of background images in Elements mode (Desktop Publisher)
  • Outline/TOC editing now available for Reflowable publications (Desktop Publisher)
  • Improved ePUB3 validation compliance for iOS book store (Desktop Publisher)
  • Improvements in how rectangle and point annotations are drawn (Classic)
  • Atom Electron framework updated to version 1.6.0 (Desktop Publisher)
  • Fixed an issue where missing background images in templates were blocking new publications from being created (Zine)
  • Fixed an issue where switching between Two-Page and Portrait in Zine could cause the viewer height to collapse to 0 in some scenarios (Zine)
  • Fixed an issue where the –proxy-server setting wasn’t respected in the desktop publisher (Desktop Publisher)
  • Fixed an issue where Google Analytics tracking wasn’t working properly when using multiple tracking codes (Zine, Elements)
  • Fixed an issue where colors would be misrepresented in print when using some Firefox versions (Classic, Zine)
  • Fixed an issue where some texts where being incorrectly stretched in when flatten/compress was turned on (Zine)
  • Fixed an issue where search abstracts would not appear in Chrome for the first page in the Elements viewer (Desktop Publisher)
  • Fixed an issue where certain grouped & scaled texts would appear incorrectly in compressed mode and Elements (Desktop Publisher)
  • Fixed an issue where two fold publications with overlapping text did not get their text adjusted properly in some cases (Desktop Publisher)
  • Fixed an issue where turning on accessible mode in Elements would not take effect (Desktop Publisher)
  • Fixed an issue where the text would be visible twice if switching into portrait from two page mode after zooming in when using compressed mode (Zine)
  • Fixed an issue where exported fonts were not being included in configuration in certain scenarios (Zine)
  • Fixed an issue where some file names received double dashes instead of single dashes when modified to a valid file name (Desktop Publisher)
  • Fixed an issue where small publications would fail to render thumbnails in some scenarios (Zine)
  • Fixed an issue where it wouldn’t be possible to enable text select on pages in certain scenarios (Zine, Classic)
  • Fixed an issue where clipped text in some documents would cause the publishing to fail in flatten/compress mode (Zine)
  • Fixed an issue where clicking external links in miniature mode would cause the viewer to blank out (Zine)
  • Fixed an issue where certain IE versions would fail to render Elements publications on FlowPaper cloud (Elements)
  • Fixed an issue where the PDFTk path was incorrect in the ASP.NET set up scripts (Zine, Classic)
  • Fixed an issue where using the SEO option with the Elements viewer and uploading to FlowPaper cloud could cause the first page url to be incorrectly updated (Desktop Publisher)
  • Fixed an issue where reopening Elements publication would cause added links to disappear (Desktop Publisher)

Next release will be at end of July/beginning of August

Monday 19th June 2017

We’re in the process of implementing new machine learning (AI) algorithms for our desktop publisher which we hope will help a lot in creating responsive publications from PDF documents. The results we’re seeing so far are very encouraging. We have been working hard on getting these in place since the start of the year under the hood and had a big breakthrough in late April when we took a new approach on how documents can be republished using unsupervised and supervised algorithms.

As we’re in the midst of this we have decided to delay next release until end of July or beginning of August. If you are waiting for something you have reported to be fixed and would like a pre-release then you are welcome to flick us an email and we’ll help you out.

All the best
The FlowPaper Team

FlowPaper 3.0.2 Release Notes

Sunday 14th May 2017

We’re super happy to announce our latest version which includes a number of improvements in both style and general bug fixes. Here’s the list of noteworthy changes this release :

  • Improved cloud service publishing to make sure it doesn’t show previous versions from cache after modifications have been made (Elements)
  • Improved the look for the Elements viewer including adding options for rounded borders options (Desktop Publisher)
  • Fixed an issue where search wasn’t closing properly on touch devices in Elements (Desktop Publisher)
  • Fixed an issue related to positioning of search matches when matching sub-strings (Classic)
  • Fixed an issue where it wasn’t possible to annotate text after performing a search (Classic)
  • Fixed an issue where some CID characters were incorrectly exported in compressed mode (Zine)
  • Fixed an issue where re-importing a PDF and turning on or off flatten/compression could cause fonts to be missing (Desktop Publisher)
  • Fixed an issue where type3 fonts were not rendered in flattened/compressed mode (Zine)
  • Fixed an issue where rotated text with negative angle would get slightly mispositioned in some cases in flatten/compressed mode (Zine)
  • Multiple style template improvements (Zine)
  • Improved viewer size for Zine when toolbar is hidden or positioned in the bottom of the screen (Zine)
  • Improved the ‘Rainforest’ theme in Zine with new icons and better positioning (Desktop Publisher)
  • Switched to using .bin as mime type when exporting in flattened mode to avoid mime type issues in certain web servers (Zine)
  • The publisher is now defaulting to use flatten/compression (Desktop Publisher)
  • The publisher will now warn if the publication contains fonts that are non-unicode when exporting to ePUB (Desktop Publisher)
  • Fixed an issue where printing ranges were not returning the correct pages (Zine,Classic)
  • Fixed an issue where some texts were classified as overlapping in compressed/flattened mode (Zine, Elements)
  • Improved SEO export settings for consistency between Elements & Zine (Desktop Publisher)
  • Removed the PHP output settings as they were redundant with other settings and not compatible with our
    cloud hosting causing confusion (Desktop Publisher)
  • Fixed an issue where the Cordova application wasn’t able to read its template properly (Desktop Publisher)

FlowPaper 3.0.1 Release Notes

Tuesday 11th April 2017

We’re happy to announce our latest version of FlowPaper with a number of great updates. We have been focusing this month at providing some clarity on how FlowPaper can improve search ranking compared to a normal PDF. FlowPaper Elements has had a number of improvements around search indexing and this version greatly improves the way Google and other search engines is able to discover sections and headers in your publications. You can try the new SEO features in Elements by ticking the “Improved SEO” checkbox under behaviour.

Changes in this release

  • In order to improve SEO, Elements is now using h1/h2/h3 tags instead of div tags for headers (Elements)
  • FlowPaper Elements is now detecting and creating a table of contents for publications if they do not have one specified in the PDF (Elements)
  • Improved font for the TOC in the Elements viewer (Desktop Publisher)
  • Improved email detection and unicode output for compressed/flattened documents (Desktop Publisher)
  • Zine now checks the proportions of the available area when deciding on viewing mode. If the viewer is very narrow but high then the viewer will choose to display a single page as opposed to two pages (Zine)
  • Improved indexing (SEO) for Elements publications so that Google and other search engines are now able to index each section separately (Desktop Publisher)
  • The rel=nofollow and rel=noopener tag added to external links in Elements publications (Desktop Publisher)
  • The elements viewer now updates the #page=(page number) name tag in the url when navigating through the publication to make sharing and returning to a page easier (Elements)
  • The Zine viewer is now able to start with TOC open if any is available (Desktop Publisher)
  • Switched to using the new analytics.js tracker for all viewers (Zine, Elements)
  • Improved pre-loading of fonts in flatten/compressed mode for Zine (Desktop Publisher)
  • Improved loading speed further by including partial content for the Elements viewer using the html5 compliant link rel=”import” tag (Desktop Publisher)
  • Improved unicode support for Chinese &B Thai languages (Classic)
  • Fixed an issue where two-fold Elements publications would have their fonts incorrectly adjusted (Desktop Publisher)
  • Fixed an issue where the Elements viewer was attempting to use the computed font style incorrectly causing the wrong font to be used (Elements)
  • Fixed an issue related to editing pages in the elements viewer where the editor would replace a page incorrectly in some scenarios. (Desktop Publisher)
  • Fixed an issue where setting a background image to Zine would cause an incorrect background color to the search abstracts (Zine)
  • Fixed an issue where setting Zoom Interval to 0.4 or higher would cause the viewer to get the incorrect initial scale (Zine)
  • Fixed an issue where self maximized hosted videos were missing the close button (Zine)
  • Fixed an issue where the search abstract would be mispositioned when going into full screen if already visible prior to entering the full screen mode (Zine, Classic)
  • Fixed an issue where the text for the last page would not load properly for the last page in certain pages when using the flatten/compress mode (Zine)
  • Fixed an issue where small PDFs would get unessicariliy copied to the docs/ directory without being needed when using the flatten/compress mode (Desktop Publisher)
  • Fixed an issue where some auto detected links for email addresses would be incorrect (Zine)
  • Fixed an issue where some animations were not being triggered in a timely fashion (Elements)
  • Fixed an issue where some texts where incorrectly clipped when exported to an Elements publication (Elements)
  • Fixed an issue where two-fold publications with uneven total page numbers were missing the last page (Elements & Zine)
  • Fixed an issue where the viewer would not be initialized properly when starting at certain page numbers (Elements)
  • Fixed an issue where it wasn’t possible to use the full range of page numbers for two fold publications when adding new TOC items (Desktop Publisher)

Improve search ranking for PDF content

Wednesday 29th March 2017

This is the first blog post in a series where we are going to explore how Google ranks PDF documents versus web content created using our upcoming version (version 3.0.1) of FlowPaper Elements. We are going to be completely transparent on how we set up our tests and why we think Google prefers using publications created with FlowPaper Elements as opposed to the PDF so that you can test and verify the results yourself and understand why.


Setting up the test

We decided that we wanted to explore how Google ranked a PDF versus the same content published as HTML5 content. So to do this we staged a little test. We created a blog post with a link to 5 different publications. Each publication converted using FlowPaper Elements and with its corresponding PDF document next to it. You can still see the blog post here. It looks like this:

The following assumptions were made around how Google would treat these links:

  1. Google would treat the PDF and the FlowPaper publication equally on a domain name basis since both are hosted under flowpaper.com. The FlowPaper Elements publication is actually hosted under online.flowpaper.com but Google treats subdomains the same as subdirectories according to themselves. Please see this Youtube link on this.
  2. Both links were added with absolute positions in the blog post to avoid having Google to rank one better than the other if it appears before the other in the layout
  3. Google would treat both equally on a file name basis since both had the same file name


Results & Analysis

We allowed a bit more than a week to pass before starting to collect results. We then decided to do 3 different tests to see how Google found content within these links. Main title, sub titles and body text searches. Below are the results of our findings. Note that we appended “site:flowpaper.com” (in italic) to restrict searches within our own domain in case the same publication would appear elsewhere.


Main title searches

FlowPaper was able to outrank the PDF in every case that we tried for main title. Here are the titles searches we performed for the publications:

  1. 2016 vacation guide site:flowpaper.com (see screen shot)
  2. 2013 annual report site:flowpaper.com (see screen shot)
  3. Yummy St. Patricks Day Guide site:flowpaper.com (see screen shot)
  4. Art & Design Magazine site:flowpaper.com (see screen shot)
  5. Think Issue 12 site:flowpaper.com (see screen shot)

So how does a PDF define a title compared to a title in FlowPaper? Well, PDFs do not contain meta data around things, so a main title in a PDF is just a larger font that typically appears on the first pages of a document. A main title in FlowPaper Elements on the other hand is an actual header tag (typically a H1 tag) as seen in the screen shot below.

Why is this important? Because according to Google, titles do have relevance to the match of where a certain page lives. FlowPaper Elements make sure that headers are real headers and that they match the title of the publication.


Section title searches

Now thats all fine you might say, because the PDFs may or may not have well defined titles in their text content, so thats a relatively easy thing to beat the PDF on. Well how about titles in sections? Titles in sections should rank high in a PDF too, but there is one major difference in how we treat sub titles and how a PDF treats them. Google claims that having too many titles on the same page would considered crud. Since a PDF contains all titles in the same document, its quite natural to think that a header that appears further down in a document would not get the same search relevance as one on the very top. Let’s have a go and see what happens within our test. We performed the following sub title searches (sub titles marked in bold):

  1. 2016VacationGuideIndexTest Leland site:flowpaper.com (see screen shot)
  2. 2013 Annual Report Grants site:flowpaper.com (see screen shot)
  3. St. Patricks Day Whiskey site:flowpaper.com (see screen shot)
  4. Design Build site:flowpaper.com (see screen shot)
  5. think_issue12 Students site:flowpaper.com (see screen shot)

FlowPaper was able to outrank the PDF documents in each and every case of sub title searches we made. How is it possible? Well, just as with the main title, FlowPaper defines each sub section of a publication with a title using a proper HTML5 tag. It also exports each section into its own HTML page and sets the title of the HTML page to correspond with each section as seen in the screen shot below.


Body Text Searches

So far so good, so how about body texts? A PDF and a FlowPaper publication contains the same body text so these shouldn’t rank differently -right? Well there is one major difference we noted briefly in the previous section. A PDF documents contains all body text in one long page per page structure and FlowPaper splits the document into sections. This means that body text in a sub section would appear higher up in a FlowPaper publication than in a PDF. Lets see what results we’re getting. The body text fragment we searched for is marked in bold.

  1. 2016VacationGuideIndexTest as with most things on the beach site:flowpaper.com (see screen shot)
  2. 2013 annual report EJAF and LoveGold site:flowpaper.com (see screen shot)
  3. St. Patrick’s day guide dancing shoes site:flowpaper.com (see screen shot)
  4. Selby’s research site:flowpaper.com (see screen shot)
  5. think_issue12 Thalassaemia site:flowpaper.com (see screen shot)

FlowPaper was able to outrank the PDF in 4 of 5 cases. Number 2 of the tests did not render any Google result from the FlowPaper publication at all (only from the PDF). Whether this was a random fluctuation or why Google for some reason decided to not index that body text is yet unknown. It could be that it will appear in a few weeks.



We have shown that FlowPaper does indeed have the capacity to improve search ranking for your PDF documents while providing accessibility and speed of loading that by far exceeds anything that a normal PDF document can deliver. In our next part we will look at how to avoid getting Google and other search engines to index and save your content using FlowPaper Elements. Keen to get your fingers on our upcoming version? Contact us via email and we’ll send you a pre-release!

Test post for 3.0.1

Thursday 23rd March 2017

This is just a test post we are using while we are doing some testing for version 3.0.1. In the meantime, check these wonderful publications!