I learned about the August 12 eclipse late.
Late enough that I was not booking a flight to Spain. Late enough that third shift in Buford was not moving out of the way. I was going to miss the thing I was writing about.
I could still build the guide.
Drone pilots had real questions. Could a normal ND filter protect the camera? Where should the aircraft sit during the important minutes? How early should it launch? What happens when the best-looking field fills with people or falls inside controlled airspace?
I had two days to answer them.
The guide went live on August 10. Roughly 48 hours later, the publisher dashboard showed 758 views. Search supplied 62 percent of the traffic. Google alone supplied 60 percent. Nearly three out of every four readers were on a phone.
New subscribers: zero.
That number bothered me more than the 758 impressed me.
The article had done what I asked it to do. It answered a timely question, ranked quickly and reached far beyond my email list. Then those readers took the answer and left.
Search had done its part. I had not.
Discovery worked. Conversion did not.
This case study is free because the lesson belongs in the open. Search can find a useful page. It cannot tell a new reader why the rest of a publication is worth following.
That second job was mine.
I am leaving the workbench open: the numbers, the decisions, the wrong turns and the checklist I will carry into the next timed story.
The eclipse guide split the result cleanly. Discovery worked. Conversion did not.
Here is the dashboard without the victory lap.
The first 48 hours
Total views: 758
Search traffic: 62%
Google traffic: 60%
Direct traffic: 34%
Email traffic: 4%
Mobile web: 74%
Desktop web: 22%
Email recipients: 92
Email opens: 27
Open rate: 29.35%
Link clicks: 2
Click-through rate: 7.41%
Engagement rate: 14.81%
Likes: 7
Public comments: 7
Restacks: 3
New subscribers: 0
Revenue: $0
Those percentages work out to about 455 visits from Google and about 561 readers on mobile.
My email list received 92 copies. Twenty-seven people opened the email. Only 4 percent of total traffic came through email. Google brought a crowd several times larger than the list I already had.
Direct traffic accounted for 34 percent. Some of that may have come from X, Notes, copied links or apps that stripped the referral information. I did not use separate tracked links, so I cannot honestly divide that bucket after the fact.
The numbers are a snapshot, not a lifetime verdict. The article was only about two days old and the eclipse was driving a short, hard burst of interest. I cannot claim the page had earned a permanent search position.
I can claim this: SEO put the article in front of people who had never heard of Drone Drifter.
Then I gave them no clear reason to remember the name.
What worked
The title answered the search
The title did not try to be mysterious:
How to Film the August 12, 2026 Solar Eclipse with a Drone (Without Damaging Your Camera)
It named the event, the tool, the date and the risk. A pilot searching the night before knew exactly what the page promised.
I am leaving that title and URL alone. When a page is already getting search traffic, changing the address for cosmetic reasons is not clever. It breaks old links and forces Google to relearn the page.
The guide dealt with decisions, not spectacle
The useful part was not telling people that an eclipse would look dramatic. Everybody already knew that.
The guide dealt with choices a pilot had to make before takeoff:
A normal ND filter controls exposure. It is not automatically a safe solar filter.
A wide drone camera is better at showing the changing ground than filling the frame with the Sun.
The launch point still needs an airspace check.
An eclipse crowd is still a crowd.
Battery planning has to leave room for a return and landing after the shot.
Those decisions gave the article a reason to exist after the headline wore off.
The place kept it from becoming a manual
The guide could have turned into a list of settings copied from camera sites.
Instead, it came back to the ground. Streetlights waking up. Water losing its shine. A church dome holding the last hard light. A town changing color while everyone looked in the other direction.
That is the part that belongs to Drone Drifter.
The deadline cut the soft parts
An event with a fixed date does not care how long I want to polish a sentence. The deadline forced every section to answer a question or leave.
That pressure helped the article.
It also hid the missing conversion path until the traffic arrived.
What failed
The article solved the problem and ended the relationship
A search reader arrived with one job: film the eclipse without hurting the camera or breaking a rule.
The article did that job.
Then it ended with a broad invitation to subscribe for more stories. That invitation could have appeared under almost any article on the internet. It did not connect the eclipse guide to a specific thing the reader would receive next.
Useful is not the same as memorable.
I never built the bridge to the rest of Drone Drifter
Someone landing from Google did not know about the small-town flight logs, airspace lessons, courthouse stories or field decisions behind the footage.
The guide needed one short bridge, not a sales speech:
Drone Drifter follows what happens before and after the shot: practical flight planning, small-town history and the decisions that turn drone footage into a story.
That tells a new reader what remains after eclipse day.
Mobile readers had to work too hard
Seventy-four percent of the audience arrived on mobile.
Several section labels were bold paragraphs instead of real headings. Long checklists were harder to scan than they needed to be. The information was present, but presence is not enough on a phone.
A mobile reader should be able to find camera safety, settings, airspace and battery strategy with a thumb and half a second of attention.
I measured promotion badly
The direct bucket was 34 percent. That is too large to shrug off and too vague to learn from.
Future X posts, Notes and email links need separate tracking. Otherwise a successful promotion disappears into “direct” and I end up guessing which platform did the work.
Event traffic borrowed urgency from the calendar
The date created demand I did not own.
That does not make the traffic worthless. It means the follow-up had to be ready before the interest disappeared. I published the guide, promoted it and only then started thinking about the permanent version.
Next time, the afterword and evergreen update get planned with the original article.
What I will change without damaging what worked
I am not rebuilding a page that Google already found. Changes should be controlled.
Keep the existing title and URL.
Turn every major section into a real H2 and every subsection into an H3.
Convert settings, mistakes and preflight items into actual lists.
Add two or three internal links where they naturally answer the next question.
Use one strong subscription invitation near the end, not buttons scattered through the article.
Make that invitation explain what Drone Drifter publishes after the event passes.
Use tracked links for X, Notes and future email promotion.
Update time-sensitive details while keeping the permanent safety and planning sections intact.
One CTA is enough if it says something.
My event-article flight plan
This is the repeatable part. Eclipse, launch, demolition, storm front, festival or courthouse reopening—the date changes, but the work around it does not.
Before writing
Name the exact question a reader will type.
Identify the decision only field experience can improve.
Separate hard safety facts from personal judgment.
Choose the permanent lesson that survives the date.
Decide what the reader should open next.
Before publishing
Put the event, date and practical promise in the title.
Write an SEO description that finishes the promise without repeating the title.
Set a clean URL before publication.
Use real headings and short lists for mobile readers.
Add one internal link to the next useful field note.
Prepare separate tracked links for Notes, X and email.
Write one specific subscription invitation.
Draft the post-event update before the event happens.
During the first 48 hours
Record total views.
Record search, direct, Substack and email shares.
Record mobile versus desktop traffic.
Record opens, clicks, likes, comments and restacks.
Record free and paid subscribers attributed to the post.
Save the snapshot before changing the title, CTA or structure.
After the event
Remove expired urgency.
Keep safety guidance and reusable planning sections.
Update the introduction for the next event.
Link the original guide to the afterword without creating two pages that chase the same search.
Compare subscriber conversion before and after the revision.
Copyable brief for the next timed story
Event:
Publication deadline:
Reader’s immediate question:
Decision this article helps them make:
Safety or legal risk that needs a primary source:
Field detail only I can add:
What remains useful after the date passes:
Article the reader should open next:
One-sentence subscription promise:
Tracked Notes link:
Tracked X link:
Tracked email link:
First 48-hour snapshot:
Seven-day snapshot:
Post-event revision date:
What counts as a win next time
I am not choosing a conversion percentage because it looks good in a marketing article. I do not have enough data for that.
The next test has a simpler job: produce a measurable, nonzero subscriber result and preserve the search traffic.
One conversion gives me a baseline. More than one gives me something to compare. Zero tells me the bridge is still missing.
The eclipse guide was not a failure. It answered real questions. It may have kept someone from treating an ND filter like solar protection. It showed that a small publication can reach well beyond its subscriber list when the page is useful and the title is clear.
But attention is not an audience.
Seven hundred fifty-eight people came through the door. I showed them the eclipse and forgot to show them what came next.
This free case study is the correction.
The numbers are open. So are the wrong turns and the field plan.
Related work
Analytics note: Figures above come from the Substack publisher dashboard snapshot taken August 12, 2026, roughly 48 hours after publication. Percentages may not sum to 100 because the dashboard groups devices and sources separately and rounds displayed values.
Subscribe to Drone Drifter for field-tested drone guides, flight logs, small-town history and honest after-action reports. I will show you the flight plan and the result.