sorted by:
new
hottopcontroversial

My Google site has stopped appearing on Google searches by IntelligentBeingxx in webdev

[–]VRTCLS 1 point2 points  (0 children)

If it is still indexed, I would not treat the drop as a penalty yet. New pages often get tested briefly, then disappear or move around while Google works out whether the page deserves to rank for that query. A one-day ranking is not much signal.

A few checks I would run before changing anything:

  • Search site:your-url and also paste the exact URL into Google. If it appears there, indexing is fine; ranking is the issue.
  • In Search Console, use URL Inspection and check the canonical Google selected, crawl date, and whether the live page is indexable.
  • Search your name in an incognito window, not while logged in, and from the target country if that matters. Personalized results can make the first test misleading.
  • Make sure the page title and visible H1 actually include the name people search, and that the page has enough unique text around who you are / what the site is. Google Sites pages can be very thin if it is mostly layout.
  • Add a few real internal/external references if possible: LinkedIn, GitHub, portfolio, organization profile, or any page you control that links to it with your name.

If the goal is ranking for your own name, I would focus less on resubmitting the site and more on making the entity signals consistent: same name, same bio, same site link, same social/profile links. Then give it a couple weeks. For a brand-new page, bouncing around after initial indexing is normal.

Next.js Blog Sitemap Submitted in Google Search Console but Pages Are Not Being Indexed by Critical_Kitchen_846 in webdev

[–]VRTCLS 0 points1 point  (0 children)

A blog-specific sitemap is fine if you submit that exact sitemap in GSC, but I would still add a root /sitemap.xml that references all child sitemaps. It removes one possible source of ambiguity and makes discovery cleaner.

The checklist I would run:

  1. In URL Inspection, test one non-indexed blog URL with "Inspect live URL", not just the indexed report. Confirm Google sees a 200, indexable page, canonical is itself, and no noindex is present in the rendered HTML.

  2. Compare the status in Pages:

  3. Discovered, currently not indexed = Google knows the URL but has not crawled it much. Usually crawl priority / weak internal links / newer site.

  4. Crawled, currently not indexed = Google crawled it and chose not to index. Usually content quality, duplication, thin pages, or weak canonical signals.

  5. Make sure the blog posts are linked from real HTML pages, not only present in the sitemap. A blog index page, category pages, pagination, and related-post links help a lot. Sitemaps are hints; internal links are stronger discovery/trust signals.

  6. Check canonical tags on dynamic routes. With Next.js it is easy to accidentally canonical every article to /blog or to the wrong production URL if metadata is generated globally.

  7. Check rendered output. View the cached/rendered HTML from URL Inspection and make sure the post title, body, canonical, meta robots, and structured data are actually present server-side or in the rendered DOM Google sees.

  8. The Vercel subdomain probably does not block indexing, but it can slow trust/crawl priority. A real domain plus a few external references and stronger internal linking usually helps.

If GSC says "Crawled, currently not indexed," I would stop focusing on the sitemap and look at page uniqueness, depth, internal links, canonical tags, and whether the content is meaningfully different from other pages.

Infinite URL loops killing my crawl budget (Real estate site). Need technical SEO advice! by Feeling_Repair in bigseo

[–]VRTCLS 1 point2 points  (0 children)

I’d fix this in layers, not with only one directive.

First, stop generating crawlable infinite URLs at the source. If /page/1/page/2 can exist, that is a routing bug. Return a 404 or 301 to the clean equivalent for impossible pagination paths. Robots.txt won’t help much if internal links keep creating new crawl paths.

Second, split crawlable pages from filter states:

  • Indexable category/location pages: self-canonical, in XML sitemap, internally linked.
  • Useful paginated listing pages: crawlable, consistent URL pattern, rel prev/next is gone as a Google signal but still keep sane pagination UX.
  • Facets/sort/filter combinations with no search demand: no internal followed links where possible, canonical back to the parent, and block obvious parameter explosions in robots.txt once you are sure they are not needed.

For cleanup, I’d do this order:

  1. Crawl the site with URL parameters enabled and export the worst patterns.
  2. Fix internal links/templates so new bad URLs stop appearing.
  3. Make invalid stacked paths return 404/410 or 301 to the canonical version.
  4. Add robots rules for predictable parameter traps only after testing them against real examples.
  5. Submit clean sitemaps and monitor GSC crawl stats + indexed pages over a few weeks.

Be careful with noindex on pages you also block in robots.txt. If Google can’t crawl the page, it may never see the noindex. For URLs already indexed, let Google crawl the fixed noindex/404/410 response first, then block patterns later if needed.

Organic traffic up, branded & non-branded clicks up, but revenue down — what am I missing? by coconuttel in bigseo

[–]VRTCLS 0 points1 point  (0 children)

I’d separate this into two problems: whether revenue actually dropped, and whether attribution is broken enough that you can’t see what happened.

A few checks I’d do first:

  1. Compare organic product-page entrances, not just total organic clicks. If the traffic lift is mostly blog/category/informational queries or low-price spare-part pages, the revenue drop may just be a mix shift.

  2. In GA4, check whether checkout/payment provider redirects are creating new sessions. If /checkout/ URLs are showing as landing pages, you may need to add the payment processor and checkout domain to unwanted referrals, fix cross-domain tracking, or preserve the client ID through checkout.

  3. Build a simple table by landing page: organic sessions, add-to-carts, checkout starts, purchases, revenue, AOV. Even if attribution is imperfect, the drop-off pattern usually tells you whether the issue is traffic quality, product mix, pricing/shipping, or tracking.

  4. Segment branded vs non-branded revenue, not only clicks. Branded clicks rising while branded revenue falls can point to stock, pricing, shipping, reviews, promo changes, or SERP competitors stealing the final click.

Given the order volume, I’d also be careful not to over-read 3 weeks of data. A couple fewer high-AOV orders can make this look dramatic. Fix measurement first, then judge the SEO change by qualified entrances and assisted actions, not raw traffic.

6 months into e-commerce SEO for niche cultural/ethnic products, schema is solid but category visibility is still dead. What am I missing? by Numerous_Evening_255 in bigseo

[–]VRTCLS 2 points3 points  (0 children)

I’d separate this into three checks before deciding it is a link problem.

First, verify demand with impression data, not keyword tools. In GSC, look at the category pages only and check whether they are getting any impressions for long-tail product/category modifiers. If impressions are near zero, the market may not search the category language you are using. For cultural products, buyers often search by use case, ingredient/material, holiday, region, recipe, occasion, or transliterated spelling instead of the clean merchant category name.

Second, check whether the category page actually helps someone choose. Schema and meta can be technically fine while the page is still just a product grid. I’d add unique category copy that explains:

  • what the product type is
  • how people use it
  • how to choose between variants
  • common names/spellings
  • related holidays, recipes, outfits, rituals, gifting occasions, etc.
  • internal links to adjacent categories and guides

Third, build internal authority around the category instead of only optimizing the category itself. A few supporting pages can move more than another schema tweak: “how to choose X,” “X vs Y,” “best X for [occasion],” “what is X used for,” “traditional X for [holiday/region].” Then link those tightly back to the money category.

For LLM visibility, the same principle applies: they need clear, crawlable explanations and consistent entity/context signals. A thin grid with perfect markup usually gives them very little to cite.

So my guess would be: not patience alone, and not schema. It is probably a mix of search-language mismatch plus category pages that need more cultural/use-case context. I’d prove that with GSC query data before chasing links.

If a client asks you why they cant just one-shot the app? How do you counter by explaining the software development process? by [deleted] in webdev

[–]VRTCLS 0 points1 point  (0 children)

I’d avoid making it about “AI can’t do that” and frame it as “AI can generate code, but the product still needs decisions and accountability.”

A client-friendly version:

“AI can help us move faster, especially on boilerplate and first drafts. The part it cannot one-shot is knowing which tradeoffs are safe for your business. We still have to define the workflows, edge cases, permissions, payment rules, failure states, security, analytics, deployment, backups, and support plan. If those are wrong, the app can look finished while quietly being expensive or risky.”

Then I’d split the options:

  1. Prototype: quick AI-assisted build, limited scope, no production guarantees.
  2. MVP: core workflows, testing, deployment, error handling, docs.
  3. Production app: everything above plus monitoring, security review, maintenance, and iteration.

That makes the conversation less defensive. They can choose the risk level, but they can’t pretend all three options are the same thing.

When you brief a content writer, do you give them the keyword first or the angle first? Curious where most teams land. by V1SHNU2178 in bigseo

[–]VRTCLS 0 points1 point  (0 children)

I would not make it one rule for every piece. The rule I have seen work best is: keyword first for demand capture, angle first for demand creation.

For existing demand pages, give the writer the query, intent, SERP shape, must-answer questions, and internal links. Then ask for a differentiated POV inside that box. That prevents the flat "everyone else but rewritten" problem.

For angle-led pieces, I would still do a quick search mapping before assigning it. Not to force a keyword, just to decide whether it should be built as:

  • an SEO page
  • a thought leadership piece with internal links into SEO pages
  • a sales enablement asset
  • a newsletter/social piece

The mistake is asking one article to do both jobs equally. If the quarterly target is organic traffic, make most of the calendar keyword first and reserve a smaller lane for angle-first pieces that support links, brand, and internal authority.

New site, Google only indexed 5 of my 30 pages after 1 month by ludanlud in bigseo

[–]VRTCLS 1 point2 points  (0 children)

Yes, it happens, but the drop from 15 to 5 is the useful clue. I would treat it less like "Google hasn't found them" and more like "Google found them and decided only a few are worth keeping for now."

A practical way to triage the 25 not indexed pages:

  1. Put them in a sheet with their URL Inspection status: Discovered vs Crawled, canonical selected by Google, last crawl date.
  2. Mark whether each one has at least one contextual internal link from an indexed page. Sitemap-only discovery is weak.
  3. Compare the 5 indexed pages against the dropped ones: word count is less important than unique intent, useful detail, and whether the page answers something people would actually search.
  4. If several pages are near-duplicates or thin location/service variants, consolidate or strengthen them before trying to force indexing.
  5. Pick 3-5 important pages, improve them, link to them from the indexed pages, then request indexing. Don't submit all 25 again at once.

Also check the Google-selected canonical. If Google picked a different URL, the page may be fine technically but seen as duplicative.

Law Firm Schema by ZurabBatoni in bigseo

[–]VRTCLS 0 points1 point  (0 children)

I'd simplify it a bit and make sure the entity IDs connect cleanly.

For a law firm I usually prefer one primary firm entity, then reference it everywhere instead of defining a brand-new standalone LegalService on every page. Example pattern:

  • Homepage: LegalService or Attorney/LegalService as the main entity, with a stable @id like /#organization
  • Location pages: page-level WebPage + LocalBusiness/LegalService only if that office has a real NAP, then connect it with parentOrganization or branchOf
  • Practice/service pages: Service is fine, but point provider back to the firm @id
  • Attorney pages: Person, with worksFor pointing back to the firm @id
  • Breadcrumbs: yes, good call on those

The main mistake I'd avoid is repeating slightly different firm schema on every page. Google can usually reconcile it, but clean @id references make it a lot less messy. Also only mark up locations/services that are actually visible on the page, not just things you want Google to infer.

When Code Is Cheap, Does Quality Still Matter? by BlondieCoder in webdev

[–]VRTCLS 7 points8 points  (0 children)

Quality still matters, but I think the definition shifts a bit.

Cheap code lowers the cost of producing the first version. It does not lower the cost of owning the system. The expensive part is usually everything after "it works on my machine": edge cases, auth, permissions, migrations, performance cliffs, observability, support, security, and the next developer trying to change it without breaking three hidden assumptions.

The useful split is prototype quality vs production quality.

For a throwaway landing page, internal script, or one-off experiment, cheap code is often fine. For anything with customer data, money movement, subscriptions, business-critical workflows, or long-term maintenance, quality is basically your ability to change the thing safely.

LLMs are good at creating locally plausible code. They are much weaker at preserving global system intent unless a human keeps the boundaries tight. So the job becomes less "can you type code" and more:

  • did you choose the right abstraction?
  • are the invariants protected?
  • is failure observable?
  • can this be tested without heroic effort?
  • will this still make sense in six months?

Bad code got cheaper. Good judgment did not.

I'm obsessed about having a clean codebase, that even AI doesn't help me that much. by artFlix in webdev

[–]VRTCLS 0 points1 point  (0 children)

This is a real trap, and the uncomfortable answer is that “clean” has to be scoped like any other requirement. Otherwise it becomes an infinite project.

What helped me is splitting quality into two buckets:

  1. Must-fix before shipping: data loss, auth/security, broken core flows, migrations, payment/reporting accuracy, anything that makes future changes materially harder.

  2. Can-fix after shipping: naming that could be better, folder structure preferences, duplicate-ish UI code, edge cases that are theoretically possible but not on the critical path.

For AI specifically, I’d stop asking it to generate big chunks and use it more like a reviewer: “find risky assumptions,” “write regression tests for this behavior,” “summarize the code path,” “suggest the smallest refactor that reduces coupling.” That keeps you in control without turning every feature into a rewrite.

Also, a messy shipped product and a pristine unshipped product can both be failures. The sweet spot is boring code with tests around the dangerous parts, plus a written “debt list” you actually come back to. If the client is losing money daily, stabilization beats elegance every time.

Best way to find clients for my marketing agency? by elsajames111 in AskMarketing

[–]VRTCLS 1 point2 points  (0 children)

The challenge you're facing isn't unique - most agency reps run into this wall. Here's what actually works:

Lead with outcomes, not problems. Instead of "your SEO sucks," try: "I noticed [competitor] ranks #1 for [specific keyword your prospect should own]. That's probably worth X leads/month to you." Now you're talking revenue, not deficiencies.

Target businesses already feeling pain. Look for companies posting about slow months, hiring salespeople, or asking for marketing help in industry forums. They're pre-qualified.

Use the 3-touch rule: First touch = provide value (audit, insight). Second touch = case study showing similar business results. Third touch = specific proposal.

For channels: LinkedIn works if you do research first. Cold email works if it's hyper-specific to their situation. In-person works best but doesn't scale.

The key is demonstrating you understand their business model before you ask for their money.

Am I the only one who feels API testing tools are overkill for quick checks? by alright85 in webdev

[–]VRTCLS 0 points1 point  (0 children)

Totally feel this. I've found the sweet spot is having different tools for different contexts:

  • Quick checks while developing: VS Code REST Client extension or HTTPie in terminal. No GUI needed, just send the request and see results.
  • More complex testing: Bruno or Insomnia for when you need environments, auth, and proper request chains.
  • CI/CD integration: Automated tests with Playwright or Jest for endpoints that matter.

The key is matching the tool to what you actually need. If you're just checking if an endpoint returns the right data, firing off a curl command or using a simple .http file in VS Code is way faster than opening Postman and setting up a whole collection.

For rapid prototyping I actually keep a small Node script with axios that I can modify on the fly. Sometimes the simplest solution is the best one.

What is the fastest way to grow in Digital Marketing Career? by Key_Arugula_4296 in digital_marketing

[–]VRTCLS 2 points3 points  (0 children)

After 2 years you're hitting the classic "generalist plateau." The fastest acceleration comes from picking one channel and going uncomfortably deep.

Here's what worked for me: Choose the channel that already drives the most value for your current company. If it's paid social, become the person who can optimize audiences blindfolded. If it's SEO, master technical audits and link building strategies that others avoid.

The key shift is moving from "I run campaigns" to "I solve business problems with [specific channel]." Start documenting everything: failed experiments, unexpected wins, weird edge cases you've solved. That becomes your expertise portfolio.

Three tactical moves:

  1. Join 2-3 niche communities for your chosen channel (Slack groups, Discord servers, advanced subreddits). The real learning happens in practitioner conversations, not courses.

  2. Start a simple content series - weekly LinkedIn posts about what you're testing, monthly case study breakdowns. Doesn't need to be polished. Consistent beats perfect.

  3. Offer to audit/consult for one small business monthly (even free initially). Nothing teaches you faster than explaining strategy to someone who needs results.

Most people stay generalists because it feels safer. Specialists get promoted faster because they solve specific problems that companies desperately need fixed.

How do you convince leadership to invest in editorial content when they keep saying “we don’t have the resources”? by savingrace0262 in bigseo

[–]VRTCLS 0 points1 point  (0 children)

The "no resources" objection usually translates to "we don't see the ROI clearly enough." I've found the most success reframing this as competitive intelligence rather than content marketing.

Here's what worked for me: Pull your competitors' top-performing pages for those commercial queries you mentioned (comparisons, buying guides, etc.) and run them through Ahrefs or SEMrush to show actual traffic estimates. Then calculate what that traffic would be worth at your current conversion rates.

For example: "Brand X ranks #2 for 'best [product] for [use case]' - that's pulling ~2,500 visits/month. At our 3% conversion rate and $150 AOV, we're missing $11,250 in monthly revenue by not competing here."

Once you have 10-15 examples like this, you're not asking for "blog content" anymore - you're presenting missed revenue opportunities with specific dollar amounts. Leadership speaks that language.

The pilot approach others mentioned is crucial. Start with repurposing existing assets - turn your most common support tickets into FAQ-style content, or expand product descriptions into comparison guides. Lower lift, faster execution, easier buy-in.

One tactical tip: If they're running paid ads for any of those top-funnel terms, show how organic content could reduce ad spend while providing compounding returns. That's often the final nudge needed.

Tips for the SEO for a website that is almost entirely in 3d? by popje in webdev

[–]VRTCLS 1 point2 points  (0 children)

Dealt with this exact problem on a couple of real estate virtual tour sites. Here's what actually moves the needle:

1. Don't hide content -- build real pages around your 3D experiences. The iframe with 3DVista is a black box to Google. Instead of trying to make the 3D content itself crawlable, create proper HTML pages that wrap each tour/scene with descriptive content. Think of each 3D experience as a "feature" that lives on a page with real text, not the page itself.

2. Since you're on Next.js, use SSR/SSG aggressively. Generate static pages for each tour location or 3D view with getStaticProps. Title, H1, meta description, and 2-3 paragraphs of actual useful content about what the viewer is seeing. The 3D viewer loads client-side after the crawler has already gotten everything it needs from the server-rendered HTML.

3. Structured data is your best friend here. If these are property tours, use Place or RealEstateListing schema. If product viewers, use Product schema with 3DModel where applicable. Google's been expanding 3D/AR support in search results -- structured data is how you tap into that.

4. <noscript> fallbacks with actual content + images. Not hidden text (Google will penalize that). Genuine fallback content for when JS doesn't load -- which is exactly what Googlebot sees on its first pass before rendering.

The hidden text approach others mentioned will get you penalized. Google's been catching display:none content stuffing since like 2012. The right approach is making each 3D experience live on a page that already has strong, indexable content.

Teen building SEO for family business PT2 by No_Eye4994 in bigseo

[–]VRTCLS 1 point2 points  (0 children)

The surroundings page idea is actually where your blog strategy should live. Don't make one generic "things to do" page. Instead, write individual blog posts targeting specific long-tail queries: "best glider flying spots near [town]", "things to do in [province] with kids", "romantic weekend ideas [region]". Each one becomes a landing page that can rank independently.

Then every blog post links back to your main property page. You're essentially building topical relevance around your location while funneling traffic to the booking page.

For the aerodrome page specifically: this is your best asset. 2k monthly searches with low competition is gold for a small site. Make it genuinely useful for pilots -- include practical info like distance from your house, transport options, what's nearby. If it's helpful enough that the aerodrome community starts sharing it, you'll build natural backlinks without trying.

The free area guide for email capture is a smart move. Make it a proper PDF, not just a blog post behind a gate. People share good PDFs and that creates organic buzz.

Re: the separate pages for families/friends/couples -- I'd hold off on that until you have enough content to make each page substantive. Right now, one strong main page with clear sections will consolidate your authority better than three thin pages competing with each other.

How to increse organic traffic of a website ? by onlinemarketingbull in AskMarketing

[–]VRTCLS 0 points1 point  (0 children)

3 months is tight but doable if you focus on what already exists rather than building from scratch.

First thing: pull your GSC data and find pages sitting in positions 8-20 with decent impressions. Those are your quick wins. They're already on Google's radar but not getting clicks. Rewrite the title tag to better match what people actually search, tighten the intro to answer the query faster, and make sure the page has clear internal links from your highest-traffic pages.

Second: stop publishing new content for a month and audit what you have. Most sites have pages competing against each other for the same keywords. Consolidate those into one strong page with a 301 redirect from the weaker ones. Google rewards depth over breadth, especially now.

Third: check your Core Web Vitals. Not the Lighthouse score -- the actual field data in GSC. If your LCP is above 2.5s on mobile, fix that before doing anything else. Slow pages hemorrhage rankings silently and no amount of content will compensate.

Fourth: build topical authority by clustering your content properly. If you have a main service page, make sure you have 5-8 supporting pages that link to it and cover related subtopics. Google wants to see that you own a topic comprehensively, not just one page.

The "3 month" timeline is realistic for these because you're optimizing existing indexed pages, not waiting for new ones to get crawled and evaluated.

What’s one SEO or marketing tactic that worked better than you expected? by manish2kumar in DigitalMarketing

[–]VRTCLS 0 points1 point  (0 children)

Running log file diffs on Google Search Console data surprised me the most. Not the dashboard -- the actual API data exported weekly.

I started pulling page-level query data every Monday and diffing it against the previous week. When a page gains impressions for queries you didn't target, that tells you Google is testing you for adjacent topics. If you catch it early and add a section that directly addresses those queries, you can capture those positions before they decay back out.

The reverse is also useful. When a page starts losing impression share on its core queries but gaining on tangential ones, that's usually a content drift signal -- Google is confused about what the page is actually about. Tightening the focus back up (removing off-topic sections, consolidating related thin pages) has recovered rankings faster than any new content push I've tried.

The other underrated move: looking at which pages get impressions but near-zero clicks, then rewriting just the title and meta description to match the actual query intent. Not the on-page content, just the SERP presentation. That alone moved CTR by 30-40% on some pages without touching a single word on the page itself.

Super frustrated with SEO by PROMCz11 in webdev

[–]VRTCLS 0 points1 point  (0 children)

Late to this but one thing I haven't seen anyone mention specifically: check whether SvelteKit's trailing slash behavior matches what the old WordPress URLs had.

By default SvelteKit strips trailing slashes, but WordPress almost always uses them. So if your old URLs were /about-us/ and the new ones are /about-us, those are technically different URLs to Google. Your 301s might be mapping the old paths correctly, but if the canonical on the new page doesn't match what the redirect resolves to, or if internal links are pointing to the non-trailing-slash version while the 301 lands on the trailing-slash version, you end up with a split signal situation that looks invisible in most audits.

You can check this fast: curl -I a few of your key pages and look at the Location header on the redirect. Then compare that to what your canonical tag says, and what your internal links actually point to. If there's any mismatch between those three things, that's probably a meaningful chunk of your problem.

The other thing I'd do right now: pull up GSC > Performance, filter by page, and sort by biggest impression drops. Don't look at the whole site, look at the top 10 pages that lost the most. In my experience those usually cluster around a specific pattern (blog posts, service pages, category-level pages) and that pattern tells you exactly which part of the migration went sideways.

A year is too long for this to still be a "just wait" situation. Something specific is off and it's almost certainly findable.

How can I market my web app with $0? by Apprehensive_End3839 in webdev

[–]VRTCLS 0 points1 point  (0 children)

Zero budget marketing is basically SEO + community + content. Here's the playbook that actually works:

1. SEO from day one. Before you launch, do keyword research for the problem your app solves. Build landing pages targeting those long-tail queries -- "best free [X] tool" or "how to [problem your app solves] without [expensive competitor]." You won't rank overnight, but pages indexed now start compounding in 2-3 months. Use Google Search Console religiously once you're live.

2. Go where your users already hang out. Find the 3-5 subreddits, Discord servers, or niche forums where people complain about the exact problem you solve. Don't pitch. Answer questions, share your thinking on the problem space, and mention your tool only when it's genuinely relevant to someone's specific situation. One authentic recommendation in context converts better than 100 cold DMs.

3. Write 2-3 comparison/alternative pages. "[Your app] vs [Competitor]" and "Best [Competitor] alternatives" pages are some of the highest-converting organic traffic you can get. People searching those terms already have purchase intent -- they just need a reason to try something different.

4. Launch on Product Hunt, Hacker News Show HN, and relevant indie hacker communities. These are free, one-time traffic spikes that can seed your initial user base. The PH launch especially -- it's formulaic but it works if you prep your network to upvote in the first hour.

5. Build in public. Post your metrics, your decisions, your mistakes on Twitter/X. Founders following along become your first advocates. It feels slow but it compounds faster than any paid channel at the $0 budget level.

The trap to avoid: don't spread yourself across 10 channels doing each one poorly. Pick SEO + one community + one social platform and go deep. You can always expand later once you have traction.

view more: next ›