Before we run the audit, we need to make sure we're asking the right questions about the right competitors to the right buyers. This document presents what we've learned about Infinite Giving's market — your job is to tell us what we got right, what we got wrong, and what we missed.
Before we measure citation visibility in the nonprofit non-cash-giving and treasury-management space, these three signals tell us whether AI crawlers can reach infinitegiving.com, tell that its pages are current, and see the pages you actually sell from. They anchor every section that follows.
Disallow: / to a second tier of AI search and citation crawlers — Grok-DeepSearch, xAI-Grok, meta-webindexer, Amzn-SearchBot, AzureAI-SearchBot, YouBot and Google-CloudVertexBot (the Vertex AI grounding crawler) — across all 206 sitemap URLs. Two high-severity findings follow: 16 of 20 content-marketing pages are older than 180 days, and no page emits dateModified or sitemap lastmod. GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Googlebot and Google-Extended are explicitly allowed./blog/where-should-nonprofits-keep-nonprofit-reserve-funds, dates to August 2022. AI-cited content is 25.7% fresher on average than traditional Google organic results (Ahrefs, August 2025). Product & commercial: unable to assess — all 28 product/commercial pages and both structural pages carry no detectable date (30 unscored), so verify those manually./robots.txt. Of the 7 crawlers this audit tracks, 6 are allowed and Bytespider is disallowed. Beyond the tracked set, Disallow: / is applied site-wide to 7 AI search and citation crawlers and 5 user-initiated browsing agents, so on those platforms none of the 206 sitemap URLs is fetchable. The sitemap itself carries no lastmod or priority on any of its 206 entries and lists /maintenance, /success, /calendly-form, /resource-landing-page and the superseded /blog/nonprofit-reserve-funds-old.AI search is reshaping how nonprofit executives, finance leaders and board members discover and evaluate a nonprofit financial platform that combines non-cash donation processing (stock, crypto, DAF grants, endowment gifts) with SEC-registered fiduciary investment and cash-reserve management built exclusively for 501(c) organizations. These are high-consideration, low-frequency purchases made by people who are not procurement professionals — an executive director or a volunteer treasurer researching "what do we do with our reserves" now opens ChatGPT, Claude or Perplexity before they open Google, and the answer they get frames the shortlist before anyone talks to a vendor. For a 2021-founded company competing against far larger brands, that shift is an opening rather than a threat: establishing visibility now locks in a first-mover advantage that compounds, because early citations become self-reinforcing as AI platforms learn which domains to trust on a question.
This Foundation Review presents three inputs the audit depends on, and asks you to confirm or correct each. First, the competitive landscape — which vendors buyers actually put next to Infinite Giving, and in which tier, because that determines who gets head-to-head query coverage. Second, the buyer personas and the pain language they use, because who initiates the deal determines the vocabulary and altitude of the entire query set. Third, the technical baseline from our Layer 1 crawl — whether AI platforms can access, date and interpret your pages at all. Content gap analysis and citation benchmarking come after the audit runs, prioritized by what actually costs you citations rather than by what merely looks missing.
The validation call is a working session with real stakes. Two kinds of decisions need to happen: (1) input validation — are the right entities in the right tiers, are the strength ratings honest, and is the buying group we've mapped the one that actually shows up in your deals — and (2) engineering triage — which technical fixes start immediately, before any results come back. Everything decided on that call is locked into the query set that drives the audit across the selected AI platforms. The Pre-Call Checklist at the end of this document aggregates every question and every engineering task in one place, so nothing gets lost between now and then.
Allow: /, after confirming intent with whoever authored the file.dateModified field in the BlogPosting JSON-LD to the Webflow CMS updated-on date and emit <lastmod> per sitemap URL from the same field; until this ships, refreshing the stale guides earns no recency credit at all./giving/daf-grants describes an instruction-and-reminder widget rather than native grant completion; if a donor can now finish a DAF grant on your page the way Chariot's DAFpay does, DAF flips from your sharpest head-to-head vulnerability to a strength we lean into across the DAF query cluster.Three things to know before you dig in: what this document is for, what you need to do with it, and how to read the confidence badges.
Purpose The Foundation Review validates the knowledge graph that drives the audit's query set — the competitors, personas, features and pain points we'll use to probe AI platforms about non-cash donation processing and fiduciary investment and cash-reserve management for 501(c) organizations. Get these inputs right and the full audit measures what actually matters. Get them wrong and the audit produces clean data on the wrong questions.
Your Job Read every section. Flag anything you disagree with. The purple callouts (like this one) are the highest-value validation points — each names a specific uncertainty and explains what changes in the audit if your answer differs from our current read. Everything you flag gets resolved at the validation call before query execution begins.
Confidence Badges High means directly observed on your site, in reviews or in category listings. Medium means inferred from category patterns or supported by indirect evidence — treat these as our best hypotheses, not conclusions. Low means speculative and specifically flagged for your confirmation.
The baseline profile every query in the audit is built from — how we name you, how we categorize you, and which products we treat as in scope.
Validate Your category description contains two distinct buying conversations: "we need to accept a stock gift" and "we need someone to manage $2M of reserves." Which one starts most of your deals — a development leader chasing non-cash gifts, or a finance leader or board fixing idle reserves? If the volumes are genuinely comparable, we build two separate query clusters with different vocabulary, different altitude and different competitors. If one dominates, we weight roughly 70% of the query set to it and re-tier the competitive set behind it — which is the single decision with the largest downstream effect on this audit.
5 personas: 3 decision-makers, 1 evaluator, 1 influencer. Personas drive the query set — each one searches differently, so who's in this list determines how the audit phrases its questions.
Critical Review Area This is the section where your correction is worth the most. Our persona set is an outside-in reconstruction from your site, category listings and the thin review record available for Infinite Giving. You know who actually joins the calls, who asks the hard questions, and who signs. If a persona here doesn't exist in your deals — or a real one is missing — the audit spends its query budget on the wrong vocabulary.
Data Sourcing Note Role, department, seniority, influence level, veto power and technical level come directly from the knowledge graph and carry the confidence badge shown on each card. Names are illustrative placeholders — they make personas easier to talk about, nothing more. Primary buying jobs and query focus areas are synthesized by us from the role plus the pain points linked to it; they're hypotheses about search behavior, and they're the fields most worth correcting. One important caveat on sourcing: Infinite Giving has effectively no third-party review corpus (Capterra shows 0 reviews, G2 carries only a handful of seller-page testimonials), so this persona set leans on your own site and category evidence more heavily than we would like.
→ Does the Executive Director sign on their own authority at your typical customer size, or does the $100K investment minimum automatically escalate the decision to a full board vote? If it escalates, we add a board-approval query stage written in governance language rather than executive-summary language.
→ This persona came from review mining, but Capterra shows zero reviews for Infinite Giving — so how many of your customers employ a full-time CFO at all, versus a fractional CFO or an outside accounting firm? If most are fractional, we rewrite this cluster in the voice of an outside advisor vetting a platform on the nonprofit's behalf, which is a materially different set of queries.
→ Can the Director of Development approve the $149/month donation page on her own signature, or does every purchase route through finance regardless of size? If she can buy it herself we promote her to decision-maker and add bottom-of-funnel pricing and platform-switching queries in fundraising language rather than finance language.
→ Does a volunteer treasurer or finance committee genuinely have to approve before a nonprofit can sign with you, or do they ratify a staff decision after the fact? If they can block the deal, we generate a full fiduciary / IPS / advisor-due-diligence query cluster in their vocabulary; if they only ratify, those queries move to Priya and Marcus and the board language drops out of the audit.
→ Dana is our only inferred persona — does a combined finance-and-operations manager exist as a distinct buyer in your deals, or is that work absorbed by the Executive Director at organizations this size? If she doesn't exist, we drop the reconciliation and gift-administration query cluster entirely rather than run it at low weight and dilute the rest of the set.
Who Else Shows Up? Three roles sometimes appear in nonprofit finance and giving-platform deals — do they show up in yours? (1) Church or ministry business administrator — Overflow and Engiven both index heavily on faith-based buyers, so if churches are a real segment for you, that role is a distinct buyer with distinct vocabulary and deserves its own query cluster. (2) Outside CPA, auditor or fractional CFO — often the person a small nonprofit asks "is this platform legitimate and will it survive our audit," which is a due-diligence query pattern we'd write very differently from a staff persona. (3) Major gifts officer — distinct from the Director of Development once an organization is large enough to split the role, and the person most likely to be searching stock- and DAF-gift mechanics at the moment a donor raises them. Who else is in the room on your deals?
6 primary + 4 secondary competitors identified. Tier assignment determines who gets head-to-head query coverage in the audit and who is covered only through broader category questions.
Why Tiers Matter With 6 primary competitors, roughly 36–48 of the audit's queries test direct differentiation — things like "Overflow vs. Infinite Giving," "best way for a nonprofit to accept stock donations without paying a percentage fee," and "nonprofit endowment management for small organizations" — while the secondary set is reached only through broader category questions. All four secondary competitors carry medium confidence on tier, and Commonfund is the consequential one: it is the incumbent answer whenever a board asks who should manage the endowment, so if most of your deals originate on the treasury side rather than the giving side, Commonfund belongs in primary and roughly 6–8 head-to-head queries move with it.
Validate Three questions on this set. (1) Who's missing? Community foundations, a local RIA the board already knows, Daffy, Donorbox or Classy — if any of those come up in real deals and aren't here, the audit never tests them. (2) Do Givebutter and Zeffy actually appear in your deals, or are they a different budget line? A nonprofit choosing between Zeffy's free tier and a $149/month page plus a $100K investment minimum may never have been your buyer — if so, dropping them frees roughly 12–16 queries for competitors you genuinely lose to. (3) Should Commonfund move up to primary? It's the only secondary that competes on the treasury side rather than the giving side, so its tier is really a proxy for which motion drives your business. Each tier move reallocates roughly 6–8 head-to-head queries.
12 buyer-level capabilities mapped: 5 strong, 4 moderate, 2 weak, 1 absent. These determine which capability queries the audit runs and where we play offense versus defense.
Accept donated stock without paying a percentage of every gift, and hold the shares in an account our nonprofit actually owns
Get our operating reserves out of a checking account earning nothing and insured above the $250K bank limit
Work with a real fiduciary who only advises nonprofits, not a software vendor and not a generalist wealth manager who treats us like a side account
Start an endowment we control ourselves, even if it's small, instead of parking it at the community foundation forever
Hand the finance committee a quarterly report and an investment policy that survives an audit without building it from scratch
One giving page in our branding that takes card, ACH, stock, crypto, and DAF instead of five different widgets bolted onto our site
Take a crypto gift and turn it into cash automatically without our board writing a digital asset custody policy first
Know exactly what this costs before a sales call, and stop losing a percentage of every large gift to platform fees
Let a donor complete a stock or DAF gift on their own in a few minutes without my staff walking them through broker paperwork
Let a DAF donor complete a grant in a few clicks on our own page instead of sending them off to log into Fidelity Charitable and hope they follow through
Have asset gifts flow into our donor database and our books automatically instead of being retyped from a brokerage statement
Run our gala, our year-end campaign, and our peer-to-peer drives from the same place we take donations
Which Three Do We Overweight? Five of the twelve capabilities are rated Strong. The audit tests all 12, but competitive differentiation queries will emphasize 3 — so we need to know which three actually win deals:
Our working hypothesis is the first three, because fiduciary advisory and cash reserve management carry the heaviest links to your high-severity buyer pains and stock processing is the door most people walk in through. Confirm or correct that ordering at the call — it decides where roughly a third of the query budget lands.
Validate (1) Are the two Weak ratings still true? We rated Donor-Advised Fund Grant Processing weak because /giving/daf-grants describes an instruction-and-reminder widget rather than native grant completion — measured against Chariot's DAFpay, which is embedded inside Givebutter, FreeWill and The Giving Block. And we rated CRM & Accounting Integrations weak because no Salesforce, Blackbaud, Virtuous or QuickBooks integration is documented anywhere on the site and Capterra flags missing contact-management capability — do those integrations exist but go undocumented? Either correction flips a defensive query cluster into an offensive one. (2) Is Fee Transparency really only Moderate? We held it back from Strong only because AUM fee tiers aren't published — "personalized quote during our first conversation" — even though the 0% stock/DAF and 1% crypto pricing is unusually clear for this category. (3) Should Cash Reserve Management and Fiduciary Advisory be one capability rather than two? If buyers experience them as a single purchase, we merge them and stop splitting the query budget across two near-identical clusters.
12 pain points: 5 high, 7 medium severity. Buyer language is how the audit phrases its queries — these are the words we'll put into ChatGPT, Claude and Perplexity, so they need to sound like your prospects, not like marketing.
Validate (1) Is "percentage fees skim the largest gifts" really only Medium? It's the one pain that maps directly onto your clearest pricing differentiator against Overflow's ~5% stock fee — if fee shock is what actually makes someone switch platforms, it moves to High and its queries move to the front of the set. (2) Does "advisor minimums price us out" come out of prospects' mouths, or is it our inference? It's our lowest-sourced pain point (inferred from category dynamics, not observed language) yet it's rated High and touches three personas — if prospects don't say it, we're building a query cluster around a problem nobody articulates. (3) Three category pains we'd expect but didn't find — do they show up? A year-end stock transfer that doesn't settle before December 31 and costs the donor the deduction; an audit or Form 990 problem from mishandled non-cash gift valuation and 8282/8283 substantiation; and a board that refuses to invest reserves at all out of loss aversion, which is a different objection from not knowing how.
A technical read of 50 pages on infinitegiving.com against a 206-URL sitemap: 9 diagnostic findings plus 1 item requiring manual verification. These are engineering and content-operations fixes, independent of anything the audit measures later.
Act Now — Engineering One finding supersedes everything else in this document: robots.txt applies Disallow: / to a tier of AI search and citation crawlers, including Grok-DeepSearch and xAI-Grok, meta-webindexer, Amzn-SearchBot, AzureAI-SearchBot, YouBot and Google-CloudVertexBot — the Vertex AI grounding crawler, which is separate from the Googlebot and Google-Extended you already allow. On those platforms, no amount of content or schema work can produce a citation, because all 206 URLs are off-limits. The policy looks deliberate rather than accidental, and the distinction it misses is the one most sites miss: per BrightEdge's April 2026 analysis, most companies focus on blocking training agents (77%) while far fewer address search agents (21%) or user-facing agents (38%). Engineering should split the file into three tiers — training, search/citation, user-initiated — keep the training blocks if that's the intended IP position, and confirm with whoever authored the policy before deploying. Two further items are engineering-owned and independent of the call: adding dateModified to the BlogPosting JSON-LD and <lastmod> to the sitemap, and demoting the boilerplate CTA <h1> in the Webflow symbol.
What we found: robots.txt at https://www.infinitegiving.com/robots.txt implements a deliberate, tiered bot policy. The largest AI platforms are explicitly allowed: GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Google-Extended, Googlebot, Bingbot and Applebot all receive "Allow: /". However, a second group is given "Disallow: /". Blocked AI search and citation crawlers: Amzn-SearchBot, AzureAI-SearchBot, Google-CloudVertexBot, Grok-DeepSearch, xAI-Grok, meta-webindexer, YouBot. Blocked user-initiated browsing agents: MistralAI-User, Manus-User, NovaAct, meta-externalfetcher, quillbot.com. Blocked training crawlers: CCBot, GrokBot, Meta-ExternalAgent, Applebot-Extended, Amazonbot, Bytespider, Ai2Bot, cohere-ai, DeepSeekBot, PanguBot, Diffbot, FacebookBot, omgili, Timpibot. Of the seven crawlers this audit tracks, six are allowed and Bytespider is blocked.
Why it matters: The blocked group is not limited to training crawlers whose exclusion has no citation cost. Grok-DeepSearch and xAI-Grok are the retrieval agents behind Grok answers, meta-webindexer feeds Meta AI, Amzn-SearchBot feeds Amazon assistant surfaces, AzureAI-SearchBot feeds Microsoft AI answer surfaces, YouBot feeds You.com, and MistralAI-User is Mistral's user-initiated fetcher. Google-CloudVertexBot is the crawler used for Vertex AI grounding, so blocking it can suppress Infinite Giving in Gemini and Vertex-grounded enterprise assistants even though Googlebot and Google-Extended are allowed. A "Disallow: /" applies to all 206 URLs in the sitemap, so on those platforms the entire site — every product page, every guide, every case study — is unavailable for citation regardless of content quality. This is a site-wide, platform-wide visibility block, which is why it is rated critical even though the four largest platforms remain open.
Recommended fix: Treat the three tiers separately rather than as one policy. Keep training-crawler blocks if that is the intended IP position. Move the search and citation crawlers — Grok-DeepSearch, xAI-Grok, meta-webindexer, Amzn-SearchBot, AzureAI-SearchBot, Google-CloudVertexBot and YouBot — to "Allow: /", since these fetch pages in order to cite them in answers rather than to train on them. Do the same for the user-initiated agents (MistralAI-User, meta-externalfetcher), which only fetch a page when a real user has asked about it. Confirm the change is intentional with whoever authored the policy before deploying.
What we found: Of the 20 content-marketing pages inventoried (17 guides plus 3 case studies), 16 carry a published date older than 180 days and 11 are older than 365 days. Only 3 fall inside the 90-day window: /blog/nonprofit-investment-policy (2026-07-02), /blog/endowments-101-what-every-nonprofit-needs-to-know (2026-06-21) and /blog/fdic-coverage-for-nonprofits (2026-05-27). The oldest high-intent pages are /blog/where-should-nonprofits-keep-nonprofit-reserve-funds (2022-08-05, ~4 years), /blog/nonprofit-reserve-funds (2024-01-29), /blog/how-donor-advised-funds-can-support-your-nonprofit (2024-09-03) and /blog/nonprofit-investment-advisors (2024-12-09). All three customer case studies are older than 500 days. The category average freshness score is 0.185 out of 1.0.
Why it matters: The stale pages are not peripheral — they are the exact pages that compete for the queries this business depends on: where to keep nonprofit reserve funds, how to choose a nonprofit investment advisor, and how DAFs support a nonprofit. AI answer engines weight recency heavily when selecting which page to cite for a given claim. Ahrefs' August 2025 analysis of 17 million citations found AI-cited content was 25.7% fresher on average than the general organic result set (cross-platform), and ConvertMate's 2025 study of ChatGPT citations specifically found 76.4% of its most-cited pages had been updated within the previous 30 days. With 11 of 20 pages beyond a year, competitors publishing on the same topics are the fresher option on most of Infinite Giving's core queries.
Recommended fix: Run a refresh pass on the oldest high-intent guides first — /blog/where-should-nonprofits-keep-nonprofit-reserve-funds, /blog/nonprofit-reserve-funds, /blog/nonprofit-investment-advisors and /blog/how-donor-advised-funds-can-support-your-nonprofit — updating figures, adding current rate and market context, and re-dating each page on publish. Fix the underlying date plumbing first (see the next finding), otherwise the refresh will not be visible to crawlers. Then set a standing cadence so no commercial-intent guide passes 180 days unreviewed.
What we found: All 20 blog and case-study pages inventoried emit a BlogPosting JSON-LD block containing "datePublished" but none contains "dateModified" — 0 of 20. Separately, sitemap.xml lists 206 URLs and not one carries a <lastmod> element. The pages also render only a single byline date in the hero, with no visible "last updated" line. There is therefore no machine-readable signal anywhere on the site that a page has been revised since first publication.
Why it matters: This is the mechanism that makes the staleness problem unfixable by content work alone. If Infinite Giving rewrites a 2024 guide today, a crawler still sees datePublished 2024, no dateModified, and no sitemap lastmod — so the page keeps being treated as years old and the refresh earns no recency credit. It also removes the cheapest possible signal for the pages that are already current. Because it applies to all 206 URLs and gates the remediation of the freshness finding above, it is rated high rather than treated as a routine schema gap.
Recommended fix: Add a "dateModified" field to the BlogPosting JSON-LD, bound to the Webflow CMS item's updated-on field so it maintains itself. Configure the sitemap to emit <lastmod> per URL from the same field. Surface a visible "Last updated: {date}" line near the byline on guides and case studies so human readers and crawlers see the same claim. All three are configuration changes in Webflow, not a rebuild.
What we found: A repeated call-to-action block, "Grow Your Giving with Expert Nonprofit Financial Advice", is coded as an <h1> and appears on most templates, so pages carry two or three H1s instead of one. Every one of the 20 guide and case-study pages has exactly 2 H1s for this reason. The homepage has 3 ("The Future of Nonprofit Finance", the CTA block, and "Latest Insights"), as do /why-choose-us and /blog/donor-advised-funds. On /roi-calculator the situation inverts: the page's only two H1s are the boilerplate CTA and "Latest Insights", so the page's actual subject is never expressed as an H1. Five inventoried pages have no H1 at all — /company/security, /frictionless-giving-checklist, /landing/cryptocurrency-white-paper, /landing/ips-template and /nonprofit-stock-donations-with-no-processing-fees. Average heading hierarchy score across the inventory is 0.52.
Why it matters: The H1 is the strongest single statement of what a page is about, and answer engines use the heading tree to decide which passage answers a given question. When a marketing CTA competes with the real title on every page, the same generic string is presented site-wide as a primary topic, diluting the topical signal of otherwise well-targeted pages. On /roi-calculator and the five H1-less pages, there is no primary topic signal at all.
Recommended fix: Demote the repeated CTA block from <h1> to <h2> or a styled <div> in the Webflow symbol — one edit that corrects every page using it. Do the same for the "Latest Insights" block. Then add a single descriptive H1 to the five pages that lack one, and give /roi-calculator an H1 naming what it calculates.
What we found: 25 of the 50 inventoried pages contain no JSON-LD block at all. The gap falls entirely on the commercial side of the site: /giving/giving-page, /giving/crypto-donations, /giving/daf-grants, /giving/endowments, /investing, /cash, /company/pricing, /company/advising-services, /company/security and all nine /who-we-serve/ vertical pages have zero structured data. Guides and case studies are markedly better served — all 20 carry BlogPosting, and six also carry a populated FAQPage. Only two commercial pages carry any schema: /giving/stock-donations and /why-choose-us each have FAQPage but no Product, Service or Offer type. The homepage, /company/about and /roi-calculator carry Organization only. Average schema coverage across the inventory is 0.47.
Why it matters: The pages with no schema are the pages that describe what Infinite Giving sells and what it costs. Structured data gives an answer engine an unambiguous, machine-readable statement of the service, its provider and its terms, rather than requiring it to infer them from marketing prose. The contrast on this site is instructive: the guides already demonstrate that the team can ship correct FAQPage markup, and those FAQ blocks are exactly the format answer engines lift most readily. The commercial pages carry several highly citable specifics — 0% stock and DAF fees, 1% crypto, up to $5M FDIC coverage, 1-3 business day liquidity — with no markup attached.
Recommended fix: Add Service or Product schema to the six /giving/* and treasury pages plus /company/pricing, with provider set to the Organization entity and the published fee terms expressed as Offer where applicable. Extend the existing FAQPage pattern to /giving/crypto-donations, /giving/daf-grants, /cash and /investing, which already have on-page FAQ sections in HTML but no matching markup. Add Organization schema to the nine /who-we-serve/ pages at minimum.
What we found: None of the 50 pages fetched contains a <link rel="canonical"> element — 0 of 50. The site does redirect the apex domain correctly (https://infinitegiving.com/ returns 301 to https://www.infinitegiving.com/), so the www variant is resolved at the HTTP layer. However, duplicate content is reachable at distinct paths with nothing to disambiguate it: /disclosures and /legal/disclosures both return 200 and are both listed in the sitemap, and /blog/nonprofit-reserve-funds-old returns 200 alongside the live /blog/nonprofit-reserve-funds. Meta descriptions and Open Graph tags, by contrast, are present on all 50 pages.
Why it matters: Without a canonical, each reachable variant of a page is a separate candidate for citation, so authority signals and any link equity split across near-identical URLs instead of accumulating on one. The superseded /blog/nonprofit-reserve-funds-old page is the sharper risk: it is live, crawlable and sitemap-adjacent, so an answer engine may cite outdated reserve-fund guidance and attribute it to Infinite Giving.
Recommended fix: Add a self-referencing canonical tag to the Webflow page templates so every URL declares its preferred form. Separately, resolve the true duplicates: 301 /disclosures to /legal/disclosures (or the reverse) and either 301 or remove /blog/nonprofit-reserve-funds-old.
What we found: sitemap.xml lists 206 URLs with no <lastmod> and no <priority> on any entry. Among them are pages that should not be advertised for indexing, each confirmed as returning HTTP 200: /maintenance, /success (a form-confirmation page), /calendly-form, /resource-landing-page and /blog/nonprofit-reserve-funds-old (a superseded duplicate of a live guide). The sitemap also includes 18 individual /team/ bio pages and 9 /blog-category/ archive pages.
Why it matters: A sitemap is a statement of which pages the site considers worth indexing. Including a maintenance page, a thank-you page and a stale duplicate spends crawl budget on URLs that can never earn a citation, and — in the case of the -old guide — actively risks an answer engine surfacing superseded reserve-fund guidance. The absence of <lastmod> across all 206 entries compounds the freshness problem covered above.
Recommended fix: Exclude /maintenance, /success, /calendly-form, /resource-landing-page and /blog/nonprofit-reserve-funds-old from the sitemap and add noindex to the utility pages. Keep the /team/ and /blog-category/ URLs only if they are intended as indexable destinations. Add <lastmod> to every remaining entry as part of the same change.
What we found: Five inventoried pages are publicly reachable and listed in the sitemap but contain almost no body copy, because the substance sits behind a download gate: /nonprofit-stock-donations-with-no-processing-fees (61 words), /frictionless-giving-checklist (75 words), /state-of-nonprofit-asset-gifts-report (86 words), /landing/cryptocurrency-white-paper (114 words) and /landing/ips-template, which renders no body content at all in the main region — the only text on the page is the site-wide legal disclaimer. Four of the five also have no H1.
Why it matters: These pages sit on genuinely valuable topics — zero-fee stock processing, the 2026 State of Nonprofit Asset Gifts report, and an investment policy statement template that speaks directly to the board-governance pain point. An answer engine cannot cite a PDF it cannot reach, so the research and the template currently generate no visibility. The asset-gifts report page even names two strong citable statistics (average stock gift of $32,000+, largest at $3M+) in its teaser, with no supporting page to anchor them.
Recommended fix: Publish an ungated HTML summary of each asset on its landing page — key findings and figures for the report, the section structure and a worked example for the IPS template — and keep the download as the conversion step rather than the only access path. At minimum, add a descriptive H1 and several hundred words of substantive on-page content to each.
What we found: In the BlogPosting JSON-LD on the guide and case-study pages, "mainEntityOfPage"."@id" is set to a bare slug rather than a URL — for example "nonprofit-investment-policy" instead of https://www.infinitegiving.com/blog/nonprofit-investment-policy. The nested "author"."url" field has the same defect, carrying values such as "karen-houghton". The pattern is consistent across the pages checked, indicating a single template that populates the field from the CMS slug rather than the full permalink.
Why it matters: The @id field is what ties a schema node to a resolvable entity. A bare slug is not a valid identifier, so consumers may discard the mainEntityOfPage relationship or fail to associate the article with its canonical URL, and the author node cannot be linked to a real profile. The markup is otherwise well-formed and populated, so this is a small fix that recovers the value of work already done.
Recommended fix: Update the Webflow JSON-LD template to emit absolute URLs, concatenating the site base URL with the CMS slug for both mainEntityOfPage.@id and author.url. Re-test a sample page in Google's Rich Results Test after the change.
The following items could not be assessed through our analysis method (rendered markdown). We recommend your engineering team verify these manually before the validation call.
What to check: The site as a whole is server-rendered — every one of the 50 pages returned complete body copy, headings and navigation in the raw HTML response, so there is no site-wide client-side rendering problem. Two pages are exceptions at the component level. /company/pricing embeds a four-question service-recommendation quiz whose questions and results are held in JavaScript objects and injected at runtime, so only the shell appears in the served HTML. /roi-calculator is a JavaScript tool of the same kind. We also observed that the pricing page ships developer instructions in an HTML comment ("ONE THING TO SET: CONSULT_URL near the top of the script block"), which is harmless to users but indicates the embed was pasted rather than templated.
Recommended action: Load /company/pricing and /roi-calculator with JavaScript disabled and in Google Search Console's URL Inspection tool to confirm what is actually indexed. If the tool content is absent, mirror the substance in static HTML — publish the quiz's service-fit logic as written guidance on the pricing page, and the calculator's assumptions and a worked example as body copy. Also remove the developer comment from the pricing embed.
Partial Sample This analysis covered 50 pages against a 206-URL sitemap — roughly 24% of what's discoverable, weighted toward commercial pages and the most recent guides. The remaining URLs are largely the 139 blog posts, 18 /team/ bios and 9 /blog-category/ archives. Two consequences worth noting: the freshness figures describe the 20 content-marketing pages we scored, and the older tail of the blog is more likely to be worse than better; and 30 of the 50 pages scored null on freshness because they carry no detectable date at all — 28 product/commercial pages and 2 structural pages — so "unable to assess" there is a real gap, not a clean bill of health. Confirming publish and update dates on the product pages is a manual check worth doing before the call.
Why Now
Once the validation call resolves the open questions, the full audit measures citation visibility across the buyer queries that actually drive this category — "where should a nonprofit keep its reserve funds," "how do we accept a stock donation without a brokerage account," "outsourced CIO for a small nonprofit endowment," "nonprofit investment policy statement template," and head-to-heads like "Overflow vs. Infinite Giving." You'll see exactly which of those queries return answers naming Overflow, FreeWill, The Giving Block or Commonfund but not Infinite Giving — and what it would take to appear in them. Unblocking the AI search crawlers and shipping the freshness plumbing before the audit runs raises your baseline before we even measure it.
45–60 minutes. We walk through this document together, resolve every purple question, settle the giving-platform-vs-outsourced-CIO framing and the competitor tiers, and lock the query set before execution begins.
We generate buyer queries across the selected AI platforms — persona-weighted, category-specific, and head-to-head against your primary competitors — then execute and capture every response and citation.
Visibility analysis, competitive positioning, and a prioritized three-layer action plan: technical fixes, content priorities (now informed by what actually costs citations), and category/narrative moves.
Start Now — Engineering Three Layer 1 fixes don't depend on the rest of the audit and will improve your baseline before we even measure it. (1) Re-tier robots.txt. Move Grok-DeepSearch, xAI-Grok, meta-webindexer, Amzn-SearchBot, AzureAI-SearchBot, Google-CloudVertexBot and YouBot from Disallow: / to Allow: /, keeping the training-crawler blocks if that's the intended IP position — and confirm the change with whoever authored the file, since the policy reads as deliberate. Crawler access for GPTBot, ClaudeBot, PerplexityBot and Google-Extended is already correct and needs no change. (2) Ship the freshness plumbing. Bind dateModified in the BlogPosting JSON-LD to the Webflow CMS updated-on field, emit <lastmod> on every sitemap URL from the same field, and add a visible "Last updated" line to guides — this has to land before any content refresh, or the refresh earns nothing. (3) Fix the heading and canonical hygiene in the Webflow templates. Demote the "Grow Your Giving with Expert Nonprofit Financial Advice" CTA from <h1> to <h2>, add a descriptive H1 to the five pages that lack one, and add self-referencing canonical tags — then retire /blog/nonprofit-reserve-funds-old and drop /maintenance, /success, /calendly-form and /resource-landing-page from the sitemap.
Two jobs before we meet. The questions on the left require your judgment — no one knows your business better than you. The engineering tasks on the right don't require the call at all.
Allow: /dateModified to the BlogPosting JSON-LD and <lastmod> to every sitemap entry