Squidbits – Greekgeek's Squidoo Blog Rotating Header Image

Squidoo NoFollows Links to Strangle Spam

Once again, spammers pooping in Squidoo's sandbox have caused inconvenience for the rest of us. Squidoo has now followed Wikipedia's example and nofollowed all outbound links.

My opinion: it stings, but on the whole it's a reasonable move. There are some drawbacks to nofollowing all outbound links. But those drawbacks are outweighed by the benefit: this will discourage those using Squidoo as a place to drop self-serving links, and encourage the use of Squidoo as a place to post actual content. For obvious reasons, Google prefers the latter.

Lakeerieartist concurs, in this succinct post on SquidLog: Spammers Be Gone.

Let me see if I can explain nofollow/dofollow links in plain English for those who don't understand what this is all about.
(more...)

Squidoo After Google Panda 25: How's It Looking?

The data is still coming in from Panda 25, launched March 15. We really need to wait a longer time to have a representative sample size, but here's the early returns from Quantcast:

Squidoo traffic vs. a similar, comparable article site, Hubpages.

From now on there will not be discreet dates on which Panda is updated; Panda is now "Panda Everflux," continually reevaluating sites and adjusting their rankings up or down. This is good, as it means Squidoo won't have to wait a month or two for Panda to reevaluate it. (The bad news is that we're only halfway through big changes from Google. There is a huge Penguin algorithm update coming which Google's Matt Cutts says will be talked about all year.)

Here's my own traffic. It looks like maybe a 7% hit from Panda 25. All told, I am down 50% since before the November 16 traffic drop that sounded a reversal of my own Squidoo fortunes for the first time since 2007.

My 6-month Squidoo traffic, Oct. 17, 2012-Mar 17, 2013

Meanwhile, my own Hubpages traffic is plodding along steadily with a temporary traffic spike from a bunch of Tolkien fans discovering one of my articles. I need to do more of those.

Squidoo is now ranked lower than Hubpages on Quantcast for the first time since Panda began in January 2011.

Squidoo took a pretty big traffic hit in summer 2007 from Google, and I feel this is comparable.

(more...)

Thin Content on Squidoo Is NOT a New Problem; Something Else Is

For years, veteran Squidoo lensmasters have been tearing their hair that some thin-content, "pile of links" lenses get promoted, showcased on the front page of Squidoo, and earn payouts, while more content-rich lenses like this sink in lensrank until they fall into WIP mode, get noindexed, and thus become invisible to search engines, cutting off their traffic.

So we should be happy that Squidoo HQ has raised the issue that we have raised for years, although I feel bad for the targeted lensmaster. But here's the catch.

Check out the recent lensrank of the lens that HQ decided to make an example of as a "spammy lens."

And here's its traffic:

Prior to HQ's Feb 27 post, what we see is the natural, organic search traffic the lens was getting. It drew daily traffic, for all that it was a pretty thin-content page. So apparently some people were finding it useful, or at least finding it.

Ironically, all the visits sent by HQ's blog post precede a next-day lensrank tumble. I suspect that some kind of manually-applied lensrank penalty may be at work, so we can't draw general conclusions from the tumble. But before that, we see that a thin-content, "list of product links" lens can naturally rank in the 15K-14K range, whereas thousands of lenses with more substantial content rank lower.

Here and elsewhere, we've seen that Squidoo's lensrank algorithm rewards lenses like the one HQ has held up as an example of what not to do. Various theories have been espoused as to why:

  • The front page of Squidoo often showcases lenses with thin content just like this one, boosting the lensrank of those lenses
  • Like exchange groups on Facebook artificially promote spammy lenses via internal traffic rather than organic
  • Soliciting of likes is now encouraged on the official forums
  • Many Squidquests tell lensmasters to run around liking lenses, and in general, the points system encourages like exchanges, so people are liking things to get points not because of content
  • Other Squidquests award points for people nominating lenses in various categories for purple stars, and so people look for and nominate random lenses in various categories to get points. Purple stars provide lensrank boosts.
  • Lensmasters now receive "angel" wings automatically, and are encouraged to bless and rank up lenses with no guidance or training to tell them what's bless-worthy
  • Fivr gigs, bots and services have sprung up selling traffic and likes to Squidoo lenses
  • ETA: When "Monsters" were added to Squidoo in fall 2010, it changed the thrust of the site from publishing content and earning readers to gaming and earning points. Is it any wonder that content has suffered, while gaming the system has increased? (Remember, before monsters were introduced, likes and blessings were anonymous).

I'm not sure which of these factors is signficant, and which are just offensive to our sensibilities but fail to have a real impact on lensrank. HQ is in a better position to judge.

The bottom line is that the top tiers are saturated with lenses similar to the one held up by HQ as "Never do this." These lenses set an example of what earns money on Squidoo. Lensmasters see them, see what gets rewarded with a good lensrank, and imitate, imitate, imitate, trying to capitalize on the same success.

At which point, telling people "don't do it!" is like wagging a finger at athletes not to take performance enhancing drugs when many news headlines, awards, and good salaries are going to stars taking performance enhancing drugs. Nothing will change until you make sure the problematic behavior is not getting rewarded.

Translation: Blame the lensrank algorithm, not just the lensmasters chasing it. And fix it.

There are bigger forces at work here, however. I can't help but see Bonnie's post in the larger context of what's been happening on Squidoo lately as a whole.

Yep, I'm talking traffic fluctuations. As usual, I use Hubpages as a comparable site and yardstick against which to measure Squidoo's traffic fortunes. Until November 2012, when Panda 22 took a noticeable bite out of Squidoo's overall traffic and rankings, Google always seemed to leave Squidoo alone and use Hubpages as a punching bag. Now, abruptly, Squidoo's traffic levels have fallen down to Hubpages' levels (and even below):


— Source: Quantcast.com

Look at mid-February. This is not a typical traffic pattern for Squidoo; in past years its traffic has been fairly steady from January through March.

This means that something has happened in the past few months. Either Google has done a massive algorithm change — in which case we'd be hearing about it across the SEO blogosphere and on these Google timelines maintained by  Sistrix and SEOmoz — or some sort of recent changes on Squidoo have caused it to fall out of Google's good graces, after years of navigating the stormy waters of Panda and Penguin without a wobble.

Are spammy lenses like the one Bonnie just fingerpointed a new phenomenon on Squidoo? No. They're annoying, and they've not helped Squidoo's reputation, but Google has never given Squidoo a hard time about them before, because Squidoo has a lot of meatier, in-depth content, too. So, if those aren't anything new, what is new on Squidoo?

The biggest recent change has been Squidoo's responsive layout redesign.

Starting in December, Squidoo redesigned the website, hoping to make it more mobile-friendly.

  • Many lenses actually became less mobile-friendly as a result, since hand-coded layouts were mangled by the change. Lensmasters have needed to go back and fix these layout problems manually, and many lenses— perhaps thousands— have not yet been fixed.
  • The responsive layout often pushes sidebar ads down to the bottom, then adds more ads to the body text area of the lens, between paragraphs and modules. This occurs not just on mobile devices, but even on very wide screen monitors and large browser windows which previously accommodated Squidoo's sidebar and body column. I've also seen extra advertising appearing at the top of lenses on my tablet.

Too much "above the fold" and intrusive advertising causes websites to be downranked by Google's "Top Heavy" algorithm. I've argued since 2011 that Squidoo's inefficient use of "above the fold" space risked incurring this penalty, yet I was wrong: somehow, Squidoo always managed to squeak by. But now that we've got ads smack dab in the body text of the lens — where Hubpages has always had a block of ads, and until now has always fared worse from Google than Squidoo has — Squidoo's traffic levels have fallen to Hubpages levels. Coincidence?

Also starting in December November, Squidoo became a Crowdignite affiliate (see Google's warnings about Link Schemes). This did three things.

  • Crowdignite links now replace the "Related lenses" box in the sidebar of Squidoo lenses, unless we specify "related lenses" manually. So before, Squidoo lenses cross-linked to good on-site content that was relevant, boosting relevance on both sides of the link and keeping pagerank within Squidoo. Whereas now, most Squidoo lenses cross-link to CrowdIgnite content that may not be as relevant and which siphons pagerank away. This is a huge SEO change.
  • Crowdignite and Squidoo are basically creating an artificial traffic exchange.  It's not a paid traffic exchange, which would likely incur some kind of penalty, but it's not something that Google recommends.
  • Moreover, to hold up its side of this traffic exchange, Crowdignite takes and republishes Squidoo content elsewhere.

This is also huge. In the past, Squidoo did not distribute lens content to other websites. But now, according to Crowdignite's TOS, "By registering a website on the Service, you expressly grant, and you represent and warrant that you have a right to grant, to Company a royalty-free, sublicensable, transferable, perpetual, irrevocable, non-exclusive, worldwide license to use, reproduce, modify, publish, hyperlink, list information regarding, edit, translate, distribute, publicly perform, publicly display, and make derivative works of all content displayed on any page of your website."

This means the content we post on Squidoo is no longer found only on Squidoo. I don't know where CrowdIgnite is redistributing our content, or how much of Squidoo's total content is being duplicated on CrowdIgnite's other affiliate sites. All we know is that CrowdIgnite is duplicating lens content off-Squidoo.

Duplicate content, folks. Again, I can't be sure this has anything to do with Squidoo's recent traffic woes, but the timing is suspicious.

However, I don't know how to test whether this duplicate content, Crowdignite's traffic exchange, additional ads, or layout problems are in fact causing Google to downrank us. Those are just educated guesses, based on my knowledge of what kinds of factors have gotten other sites clobbered by Google algorithms in the past.

So how does this tie back into Bonnie's post about spammy sales lenses?

Squidoo has a traffic problem. Its traffic and revenue are falling. I was waiting to see what kind of steps HQ was going to take to address this problem.

While I worry that too many thin-content lenses like the one Bonnie fingerpointed could lead to Google penalties, they have been part of Squidoo for years and have not cost Squidoo.com any Google rankings; they simply took away Squidoo tier payouts from other, possibly more deserving lenses. Whereas now, it looks like something else is costing the site Google rankings. I hope HQ is investigating what that "something else" might be.

[UPDATE: HQ has now identified at least one possible culprit: a recent flood of "spun lenses."]

Add Photos to Tweets to Get More Clicks!

When I browse Twitter, I see PICTURES with some Tweets, which help draw the eye to them:

Why, yes, Twitter thinks I'm weird. (Here's the Sea Slug Article and my phone book article.)

 

Hubpages, Squidoo and other websites usually have Tweet buttons, but one thing they DON'T usually do is incorporate a photo or graphic into the Tweet. If you're Tweeting your own stuff, be sure to add a graphic! Here's how:

  1. Save a graphic from the article (or some appropriate graphic) to your computer.
  2. Go to the article and click the Tweet button to compose a Tweet.
  3. Instead of sending the Tweet then and there, COPY the text of the Tweet, so that you grab the article's URL.
  4. Go to twitter.com and paste the Tweet in the Compose box.
  5. Click the camera icon at the bottom of the Tweet box to upload the photo.
  6. NOW Tweet it!

Wait— WHERE will these graphics show up, anyway?

  • Sometimes they're thumbnails in people's Twitter stream.
  • They appear in the "Gallery" area on the left side of your Twitter Profile Page.
  • They are big and bold in the "Discover" part of Twitter— click the "Discover" link at the top for a demo!
  • Twitter is evolving. I suspect these pictures are going to grow more prominent with time, so get in the habit, right now.

Obviously, be careful of copyright. Remember that the image may be shared in retweets. Do you have the right to share/publish/distribute that graphic? Or, at the least, is it Fair Use?

P.S. I've just found two treasure troves of vintage, out-of-copyright images that require no credit: Vintage Printables, which includes this odd balloon illustration, and OhMeOhMy Vintage. There you go!

Leopoldo Galluzzo's illustration for an 1836 hoax purporting to depict discoveries of life on the moon by famous astronomer John Herschel.

A New All-CSS Amazon / Zazzle Button

I hadn't posted this until now, because I'm still getting the kinks out. But I thought I'd share some CSS wizardry.

Problem:

My old Amazon "Buy" Buttons look a little fuzzy at modern screen resolutions, and they don't resize well.
Amazon Associates

Also, that's just for Amazon. Sometimes I want a Zazzle button!

I believe in the marketing research that shows a "Big Orange Button" helps convert sales.

So how can I make a BOB that will scale to different screen sizes?

Solution:

Create a rounded-corners button with CSS:

Buy on Amazon

 

 

blizzard of '78 t-shirt
Buy T-shirt on Zazzle

I'm still fine-tuning this, but people who know code can play with it.

Here's an example from my spruced-up "Blizzard of '78" lens.

Here's a template for the button. You MUST change the width (11em) to fit the width of whatever words you use. For example,  in"Buy on Amazon" button, I used 8.5em.  An em is simply the width of the letter m, so this means that the dimensions listed in ems will scale up and down to match the text.
<a style="display: block; margin: 5px auto; width: 11em; color: #fff; text-decoration: none; font-family: Arial; font-size: 90%; font-weight: bold; text-align: center; border-radius: .5em; padding: .2em; background-color: #f90; box-shadow: 1px 1px 2px #888888; background-image: linear-gradient(to top, #FF9900 60%, #FFBB44 100%);" href="LINKgoesHERE">Buy T-shirt on Zazzle</a></p>
I was a bit haphazard in which dimensions I specified in pixels, which in ems. I think this looks good at different screen resolutions, as I've checked with my iPad and this Responsive Design Tester, but... I can't promise.
Breaking it down:
  • display: block; turns the span into a block-shaped area with specific dimensions.
  • the margin is whitespace around the outside of the button. Use margin: 5px; if you do NOT want the button centered horizontally (auto)!
  • the width is the width of the orange button, which I defined in terms of the width of the letters inside. This way the button grows or shrinks with the font and screen size.
  • color: #fff makes white letters; after this comes a bunch of optional text-tweaking.
  • border-radius: makes rounded corners on most modern browsers. On older browsers, you get rectangular corners, which isn't too bad.
  • padding puts space between the borders of the orange rectangle and the words inside.
  •  background-color #f90 makes Squidoo Orange.
  • box-shadow: is a new CSS3 property, supported by IE9+, Firefox 4, Chrome, Opera, and Safari 5.1.1. On older browsers, no shadow. The values are: horizontal offset, vertical offset, blur distance, color.
  • linear-gradient: In theory, this will add a bit of shading, with darker orange at the bottom and lighter orange at the top. It's part of CSS3, but not all browsers support it... yet. They will. In the meantime, I could go with all sorts of complicated code to make it work. But I'm not gonna. There's nothing wrong with buttons that look good now, and will look better down the road.

Here's a demo of how this button looks on browsers that DON'T support the linear gradient, and those that DO. (Modern editions of all browsers support rounded corners and drop shadow; older IE will just show an orange rectangle with no shadow.)

The Mobile Web on Squidoo and Hubpages

Yep, it's another geeky stats post trying to figure out "what's going on with our traffic?"  using two similar article-publishing sites to contrast and compare trends.

Squidoo launched its "responsive" layout on Friday, December 7, 2012, hoping to cash in on the skyrocketing use of mobile devices to browse the web. Many of us had emailed HQ about the need to adapt to mobile/tablets over the past few years, so we certainly understood the reasons for the change, if not the timing. But the proof is in the pudding. How did the Responsive Layout launch impact traffic?

I'm kicking myself for not doing a screengrab of Quantcast's traffic tracking before the changeover, showing what percentage of Squidoo visitors came in through mobile, but I've at least got that info from my own Google Analytics (see below).

However, we can do a current comparison of Squidoo vs. Hubpages mobile traffic.

But first, a baseline. Quantcast shows that Squidoo's overall (mobile and desktop) traffic remains above Hubpages — barely — although it has been dropping for a few months. Squidoo is probably more dependent on holiday shopping:

Squidoo traffic vs. Hubpages traffic, August 2012 through Feb 2013.

Quantcast only gives 1-month data for mobile, but I've seen that Hubpages has always drawn more mobile traffic than Squidoo, despite having slightly less traffic overall for most of the past two years. Even after Squidoo's responsive layout update, this is still true...

(more...)

Updating Squidoo Lenses: My 2013 Checklist

Squidoo progress Excel Spreadsheet

My yearly progress spreadsheet helps me track progress and seasonal trends.

Whew, 2012 was quite a roller coaster of a year for me on Squidoo and beyond.

The good: I achieved a 68% increase in online earnings, and I began an earnest push to diversify beyond Squidoo, and succeeded at least a little (see bottom of my payouts chart).

The bad: Pinterest members began copying and uploading our photos en masse, so that we were competing with ourselves for image traffic, and third-party websites began using pinned images to make money. Hubpages, where I've had the most luck in diversification, had its Google ups and downs and its share of disruptive policy changes. Later, along with many Squidoo members, I lost 34% of my Google traffic to Squidoo around November 15. Accordingly, my November Squidoo earnings saw a 33% drop, when normally my November earnings are up. December saw a couple of Squidoo Surprises that required emergency triage to all our lenses. Also, the old by-and-for-lensmasters SquidU community was closed down by HQ and resurrected by Christene.

I'm tired. I've been tired. All of the above, plus arthritis, have left me exhausted and discouraged. So I've been taking a break from Squidoo and article sites in general. However, January's almost over, and it's time to get back in the saddle.

This year, rather than writing new content on Squidoo, I'm mostly going to write elsewhere and just do maintenance on my Squidoo portfolio.

Here's a checklist of what I do to update each lens. I'm not gonna do all these changes on every lens all at one sitting. Instead, I've created an "Update log" spreadsheet with "type of update" as the column headers, lenses as the rows. When I make an update, I'll note it in the appropriate column/row with the date.

(more...)

Cheat Sheet for Dealing With Squidoo's New Flexible Layout

My CSS Cheat Sheet for Converting Fixed-Width into Flexible Layouts

Originally posted here. (Now tweaked and revised.)

  • The first thing you should do is ask yourself, "Is this CSS absolutely necessary, or can I drop it?" See the postscript below for tips about how and when to use CSS. Usually, the best solution is, "Drop it!"
  • Testing: Try Screenfly Emulator or Responsive Layout Emulator, or if both of those are being crabby, drag the right-hand edge of your window around to simulate different screen sizes.
  • Replace font sizes and line heights in pixels with points or percentage. (E.g. 110% = "a little larger than the standard font size.")
  • To center an image or a paragraph horizontally, use style="margin: 0px auto;"
  • <br style="clear:both;"> breaks you out of float-mode and usually stops things from spilling into places they don't belong. (The "zigzaggy" stairstep effect, e.g. For that problem, put <br style="clear:both;"> between each "step" of the staircase.)
  • Convert your old fixed-width dimensions by doing a little math. Say you used to have a paragraph 250 pixels wide. Squidoo's old column width was 590 pixels. 250 ÷ 590 = .42, so change width:250px;   to width:42%; 
  • If all the widths of elements in a horizontal area add up to more than 100%, the last item will wrap onto the next row. This sometimes happens if you've got small elements like borders adding a few pixels of width to your total. In that case, trim the width of the elements you can control by 1-2% to leave more wiggle room.
  • You may need to set the outermost container width to 100%. If something's shrinking to fit, and you want it to extend to the margins, that's what to do.
  • When using percentages, you usually have to specify a paragraph or image's size in width rather than height. Percentage of the containing area's height is meaningless, because the bottom of the page is usually off the bottom of the screen. Percentage of the containing area's width makes sense, because the right margin of a page is usually visible.
  • The only time you dare specify height is with graphics small enough that they're not likely to spill into the margin even on phone-sized screens. Use Dee's handy-dandy Screenfly emulator to check.
  • Let borders and rounded corners remain fixed-width (pixels). They are usually not big enough to spill over onto the margins, and they behave quite oddly when changed to percentages.
  • Advanced: When doing side-by-side layouts, consider using the style attribute min-width: 200px; to say, "don't shrink this image (or design element) smaller than 200 pixels." On small phone screens, which are 240 or 320 pixels wide, this will force side-by-side layouts to switch to a single column, so you don't end up with teeny tiny images. You may also set a max-width, if your images start looking silly at large sizes.
  • Advanced: If you've got a colored or bordered paragraph containing a floated graphic and text, you will find that the floated graphic tends to spill out past the bottom of the paragraph when you switch dimensions to percentages. The best solution is to get rid of the color or border on the paragraph. But if you really, really have a good reason for the colored paragraph, this worked for me: <p style="background-color: #eee; width:100%;"><span style="display: block;"><img src="blah" style="float: left; blah blah;">Text text text</span><br style="clear: both;"></p>
  • Advanced: 3-items-across layout for Zazzle & other affiliate items: <p style="width: 25%; padding: 2%; margin-right: 2%; margin-bottom: 2%; text-align: center; font-size: 80%;"><a href="productLink" rel="nofollow" style="text-decoration:none;"><img src="imgURL" alt="altname" style="width: 90%; margin: auto;"><br>ProductName<br><b style="margin:auto;display:block;width:60%;line-height:110%; font-size: 70%; color:#fff;background-color:#f90;border-radius: 4px; padding:2%;">View on Zazzle</b></a></p>

Postscript: How and When to Use CSS

CSS commands, the style="blah blah blah"  part tucked inside of an HTML <tag>, let you control visual decoration and layout separately from HTML. If HTML says, "this is a hat," CSS says, "size 10 with a red brim." If HTML says, "this is a brick," CSS says, "move it two inches to the right." If HTML says, "this is a paragraph," CSS says, "200 pixels wide with a dashed border and gray background."

People tend to use CSS for decoration, but in fact, it's better to use CSS only to indicate units of the page that function in a special way.

For example, adding color to links is more than mere decoration; it informs the reader that these words are links. A side-by-side display of product images with captions under them acts like a store display, telling the visitor, these are products, and allowing the customer to compare, browse, pick and choose. It's functional, not just for pretty.

I have mostly avoided using colored or shaded paragraphs except for one special purpose: quotations or excerpts, when I'm alternating between quoting something and commenting on it. What's the function of that CSS? Its purpose is to make clear which words are mine, which words are someone else's. And I'm only going to do that on a page where I'm alternating between the two, not a simply one-off quotation or occasional quotes.

I also use CSS for navigation elements, on rare occasions. Usually, the navigation options like the "Table of Contents" in the introduction module are adequate, and don't need to be replaced.

I wasn't always this strict about CSS. So in reviewing old lenses, I've been asking myself, "Is this CSS providing useful information to the reader? Is it functional? Or is it just a paint job?" I'm dropping 99% of my "decorative" CSS. That very especially includes colored and bordered paragraphs, which are the web equivalent of a reader marking a book's text with  colored highlighter pens and underlines.

Recovering From a Squidoo Surprise

Here we go again

As most members know by now, Squidoo just unleashed a dramatically different layout two weeks before Christmas. This fits a pattern: Squidoo typically launches changes with little or no warning (that one was released on December 21, 2010, and it managed to throw some top-earning lenses into WIP, hiding them entirely from view and killing their tier earnings for the month.) Clearly, Squidoo thinks we have far too much time on our hands during the holidays.

If you've got hundreds of lenses, it may take days to salvage and check all of them. So how do we prioritize? Well, I've discovered a handy Excel trick to list all our lenses in order of how much they earn, which can aid in triage assessment.

But first, let's look at some possible ways to repair layout problems caused by this so-called "Responsive" update (as a major iPad user, the old Squidoo layout gave me no trouble, whereas this one does):

  • [UPDATE] SquidTool's creator A3 Labs has been on the ball and has updated SquidTools to work with Squidoo's new layout. See this announcement post from A3 Labs explaining the fixes, and/or Annie's tutorial on how to get these repairs to fix old Squidtools layouts.
  • For what it's worth, most of my templates from my Amazon Associates Links Tutorial seem to be working under the new layout. Exception is the five-items-across. The rest are flexible enough to cope with varying screen sizes.
  • Create smallish fixed-width building blocks that flow and wrap around like the words in this paragraph when they hit the right-hand margin. By "building blocks," I mean a box-shaped unit such as one image plus its caption underneath and maybe a "buy" button. My How to Align Image Side-by-Side templates all work this way, and as far as I can see, I think they're all still behaving correctly.
  • One might be able to change dimensions to percentages, so that layout elements stay proportional to the page width. For instance, with a three-in-a-row layout, set the width of each of the three "building blocks" to 30% with a margin-right of 2% to give a little padding and still leave a smidge of wiggle room for borders.  But there's a problem with this, too, as kburns notes: 30% of the screen width on a smartphone is tiny, too small for images. [UPDATE: See my next post: Cheat Sheet for Converting fixed-width to flexible-width Squidoo layouts. I think I've gotten the hang of it now.]
  • People who really know CSS backwards and forwards may find that some percentage-width problems are solved by adding max-width or min-width: making bits of a layout stretchy and flexible, but not infinitely so.

WHATEVER YOU DO: Keep in mind that Squidoo's width and font sizes now vary on the fly to fit people's screens and devices, so you can't assume anyone else's column width will be the same as it is on your computer. One quick way to check is to grab the lower right-hand corner of your browser window (if you can) and drag it left and right to view the lens resizing itself to fit the new window size. Also, check Screenfly (thanks, dee) to see how it will look on an iPad and other devices.

NOW, ABOUT THAT TRIAGE:

This was what I was going to post before I got distracted trying to solve layout issues (note: I cannot answer any more questions now, as I've only managed to check/repair 11 of my 431 lenses since yesterday and I've gotta get back to them).

If you have over a hundred lenses, it seems daunting to figure out where to start. Here's a five-minute exercise you can do with Excel to help you find and prioritize your top-earning lenses on Squidoo.

  1. Go to the big blue Dashboard Stats tab. (that link takes you there.)
  2. Choose "My Payments" and "Life to Date" in the pulldown menus at the bottom, and click "go". Go to the bathroom while that loads in. [UPDATE: you might want to set it to "Previous 3 months" instead; old lenses may have earned more historically, but may not be top earners now.]
  3. Click "Download report as TSV" at upper right-ish.
  4. Open the result in Excel.
  5. Select All, then, under the Data > Sort... box, Sort By Lens Title (or URL).
  6. Choose "Subtotals" under the Data menu and click OK.
  7. Now at the top of the left-hand corner, you should see buttons for "1 2 3." Click the 2, and it should hide all the different month-by-month payouts for each lens and show you just the total lifetime earnings for each lens. (If you can't find the numbers, under the Data > Group and Outline submenu, choose "hide detail" to collapse everything and then "show detail" to get the summary. This is dumb but it works.)
  8. Under the "Data" menu, choose "Sort" again and Sort by "Total," Descending.
Of course, this only tells you about Squidoo earnings, not lenses that earn most of their income through affiliate sales with third party programs like Amazon. On Amazon, you could perform the above procedure on their Earnings Reports, which could at least tell you what items are selling most on your lenses.

Keyword Research and Competition: Something Else to Consider

A lot of us do a basic form of keyword research of one kind or another, using tools like Google's to learn what search phrases are relevant to our topic and how often those phrases are searched.

By using the words real people use to search our topic, we have a better chance of getting search engines to send us those visitors. Obvious, right? Keyword research is all about finding a common language with our readers.

 

(more...)