
GeekBlog.net is an independent technology publication written for readers in the United States. We cover AI, phones, computers, wearables, gaming and the companies behind them, and we explain what each story means for the person who actually uses the product. Every article carries the byline of the writer responsible for it, and every correction is made in the open.
GeekBlog at a glance
- Audience: US readers who want clear, practical tech coverage
- Coverage: tech news, AI and software, mobile, how to guides, smartwatches and gaming
- Writers: Ethan Caldwell, Marcus Bennett and Olivia Hartman, each publishing under their own byline
- Funding: display advertising and clearly disclosed affiliate links
- Corrections and tips: contact@geekblog.net
- Publisher: BDK Media Daniel Bihun
Our mission
Technology coverage tends to split into two extremes: press releases repeated word for word, and specification sheets nobody can read. We aim for the useful space in between. Every story on this site is written to answer three questions. What happened? Is it verified, and by whom? What changes for you, in practice?
That applies whether we are reporting a security incident, explaining an AI company’s finances, comparing phones or walking through a settings menu step by step. If a story does not help a reader understand or decide something, we do not publish it.
What we cover
- Tech news. Product launches, company decisions, regulation, outages and security incidents, from the US and worldwide.
- AI and software. Assistants, models, creative tools and platform updates, with attention to what they cost and what they do with your data.
- Mobile. Android and iOS, carriers, chipsets, battery and camera behavior, and the features people actually use.
- How to guides. Step by step instructions for fixing, configuring and getting more out of hardware and software.
- Smartwatches and wearables. Battery life, health features and the apps worth installing.
- Gaming. Consoles, handhelds, PC hardware, performance and the business behind the games.
A few examples of the kind of work readers return to: our beginner guide on how to use Google Gemini, our explainer on when Anthropic is going public, our roundup of the best Google Pixel phones of 2026 and our look at Apple Watch Series 12 battery life in real use.
Editorial standards and fact checking
Our reporting is based on primary sources wherever they exist: company announcements, regulatory filings, court documents, changelogs, security advisories, published research and our own testing. When we build on the work of another outlet, we name it and link to it. When something is reported but not confirmed, we say so in the text rather than presenting it as fact.
How we check a story
- Numbers, dates and quotes are checked against the original source before publication. If we cannot find the original, we attribute the claim to the outlet that reported it or leave it out.
- Prices and availability are checked on the date of publication and marked as such, because they change quickly.
- How to guides are checked against the current version of the software or device. When a menu or feature changes, we update the guide.
- Sources are listed at the end of news and explainer articles so readers can verify them.
Updates to older articles
Technology stories age fast. When we refresh an article with new facts, we add a dated update note explaining what changed. We do not quietly rewrite history: if an earlier version was wrong, the note says so.
Tools we use
We use software tools, including AI assisted research and drafting tools, in our production process. Every article is reviewed and approved by a human editor before it is published, and responsibility for what appears on GeekBlog rests with our editorial team, not with any tool.
How we correct errors
If we get something wrong, we fix it. Send the article URL, the passage you are questioning and, if you have one, a source to contact@geekblog.net with “Correction” in the subject line. We check every report.
- Small fixes such as typos or broken links are corrected without a note.
- Substantive corrections, meaning anything that changes a fact, figure, quote or conclusion, are corrected and noted on the article itself.
- Accurate reporting is not unpublished on request. If a story is accurate, we will consider adding context or a response, but we will not remove it.
Independence and how we pay for it
GeekBlog.net is free to read. It is funded by display advertising and by affiliate links, including the Amazon Services LLC Associates Program. If you buy something after clicking one of our links, we may earn a commission at no extra cost to you.
Commercial relationships never decide what we publish or what we conclude. Advertisers do not see articles before publication, cannot request changes and cannot have coverage removed. Sponsored content is labeled on the page, and we do not sell links inside editorial articles. When a company lends us a product for review, we return it or disclose that we kept it. The full disclosure is in our Disclaimer.
Who writes here
Articles are published under the name of the writer responsible for them, and each byline links to a profile page listing that writer’s recent work. Our current bylines are:
- Ethan Caldwell, writer and editor
- Marcus Bennett, writer and editor
- Olivia Hartman, writer and editor
The full list, with each writer’s articles, is on our Authors page, which you can reach from any byline. GeekBlog.net is published by BDK Media Daniel Bihun. Our Terms and Conditions, Privacy Policy, Editorial Policy and Cookie Policy are also linked in the footer of every page.
Contact us
One address reaches the whole team: contact@geekblog.net. To help us route your message, start the subject line with one of these words: Correction, Story tip, Feedback, Press, Partnership, Privacy, Copyright notice or Security. We read everything, and we reply when a message needs an answer.
If you are reporting a security issue affecting our site, please include enough detail for us to reproduce it and do not publish it until we have had a chance to fix it.
Logo and brand assets

Journalists and partners are welcome to use our logo when referring to GeekBlog. The full size files live at geekblog.net/logo.png and geekblog.net/cover-photo.png. Please do not alter the colors or proportions.
FAQ
Who owns GeekBlog.net?
GeekBlog.net is an independent publication published by BDK Media Daniel Bihun. It is not owned by any technology company or manufacturer.
Is GeekBlog sponsored by the companies it covers?
No. Advertisers and affiliate partners have no say over our coverage. Any sponsored content is clearly labeled, and we do not sell links inside editorial articles.
How do I report a mistake in an article?
Email contact@geekblog.net with “Correction” in the subject line, the article URL and the passage in question. Substantive corrections are noted on the article.
Can I pitch a story or send a product for review?
Yes. Use “Story tip” or “Press” in the subject line. We cannot cover everything, and receiving a product does not guarantee coverage or a positive review.
Thanks for reading GeekBlog. If something we wrote helped you, or missed the mark, we want to hear about it.
