Interesting question. I've never seen someone asking about this before.
Generally, one is going to need to login before viewing a viz on Tableau. Even when one doesn't, the viz would need to be rendered and the spider/agent would need to know how to consume the dashboard in question...not a trivial task.
Can you explain why you're doing this and perhaps give us a bit more information about WHO you hope will find these vizzes?
Thanks for your reply, and apologies for being slow to spot it.
I work for a news site called Breakingviews, and we're targetting an audience in the financial sector. The kind of viz I have in mind is something like our monthly China index, tracking the Chinese economy - http://graphics.thomsonreuters.com/16/01/bv-tealeaf/index.html - As you can see, we've placed the Tableau graphic within a frame with some more info and buttons. All our graphics will be published like this to allow us to add branding and extra detail, etc.
In a perfect world, anyone searching for "Breakingviews Tea Leaf Index" or for less specific yet relevant queries such as "china economy index" would find this in their search results. And ideally, they would find the most recent version, not the previous month or year's edition.
All advice much appreciated!
PS - I must stress again that I'm one of the less proficient Tableau users. V v new to this programme. So please do feel free to answer in the simplest possible terms. Thanks!
1 of 1 people found this helpful
I've never experimented with this, but I'm pretty sure that content within a viz can't be indexed by search engines. Dustin Smith might be able to comment more on this, however.
My advice would be to approach SEO by adding your standard clickbait keywords and metadata to the containing page - you can be sure the container itself will get crawled.
2 of 2 people found this helpful
As to your questions...
Katrina Hamlin wrote:
1. I'd like to understand the principles of how to boost my Tableau offerings SEO credentials, so I can keep that in mind next time I publish something new.
2. I have an existing project which I am updating and re-publishing on a monthly basis. I am creating a new version and a new link each time, as I need to be able to link back to the previous version. So, there are multiple versions online, and as well as boosting each new edition's SEO performance, I need to find a way to try and make sure the very most recent version rises to the top of the search results. Is there any way to do that?
Russell is essentially correct here that trying to increase your embedded Tableau viz's SEO attractiveness by changing elements of the dashboard itself in Tableau isn't going to have any effect. I just chatted with Tableau's current SEO specialist here in marketing (who is also a pro Tableau user) and his report is as follows:
- While companies like Google can technically scrape certain values from an embedded Tableau viz when it is indexed, it's not something they do / it has no effect on ranking.
- Trying to add additional terms into the embed code will have virtually no positive effect and could actually hurt your SEO ranking if Google mistakenly thinks you're trying to fool it's search indexing
His advice is to readjust your focus somewhat...
- Focus on an overall good page & site SEO strategy with strong page headers, solid link links, and lots of interactive content.
- Google already detects the Tableau embedded viz as an interactive element within a page and weighs that more heavily - so right off the bat you're starting strong
- Make sure your viz is well integrated into the text narrative on the page. Increasing dwell time for readers is always a good thing and if your story is referencing parts of the viz and causing people to go back and explore the data, then you'll see longer overall session times.
The only other piece of advice is that for Tableau Public views like this, Google indexes the actual Tableau Public page it lives on if you've allowed for it to be viewed. Making a great title and filling out the description field (example) can actually improve search rankings for that page. I've seen other news agencies actually take advantage of this and insert a url in the description at the bottom that points to the article page itself. More or less it is another inbound link to the article and another pathway for readers to discover the full site where vizes are embedded on.
Hope this was helpful.
Hi Dustin and Russell,
This is exactly what I was looking for - v clear and actionable tips. Thank you!
If you think of other cool tips later, please do come back to the conversation and drop me a line. I'll do the same if I hear any more bright ideas.
I went ahead and marked Dustin's answer as correct. This raises this question and answer in our community search results and because of the unique nature of the question, I am sure it will get plenty of future views. Let us know how it goes.
I don't think Dustin said it explicitly but if the embedded view that is on public will be replaced monthly, try to keep the url for the article persistent. A persistent URL with updated information monthly will keep your SEO values high between versions rather than having to start fresh each month with a new url. That was probably understood already but just making clear.
Best of luck.
1 of 1 people found this helpful
Dustin's post is 100 correct, but I'd like to add a little to it for those who are able. This is going to get a little technical, so apologies to everyone who isn't this tech savvy. If you'd like a simpler solution, then I've added an Idea which would make this solution part of the product instead of the workaround. Please vote on that here.
Right now, implementing this is limited to users who have the ability to edit the html of the website on which they are embedding their viz. If you can't edit the html, you probably can't use this workaround.
Copy the markup and paste it into the content container in which you're posting your workbook.
Publish your page.
Test your markup with this structured data markup validation tool.
If that's a little opaque, then this guide can help you better understand structured data.
I hope this helps some of you. And again, if it sounds like this would provide value but you can't manage the work around-- vote on the idea to support product-level implementation.
This is huge deal! Josh thank you for jumping in this with tidbit. Time to go vote for that idea.