Property [title] does not exist on this collection instance

Property [title] does not exist on this collection instance

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

Property [title] does not exist on this collection instance

When debugging Laravel blade templates, one of the most frequent stumbling blocks is confusing single model instances with collections. The error message Property [title] does not exist on this collection instance is a direct indicator that your view expects an object with specific properties, but it is receiving a collection (an array-like wrapper) instead.

In the scenario provided, the developer attempts to retrieve data using Page::where('page', 'about-me')->get(). This method always returns an Eloquent Collection, regardless of how many records are found. Even if your query matches exactly one row in the database, the result is still a collection containing a single model instance. Consequently, accessing $about->title attempts to read a property directly off the collection object rather than the individual model inside it.

In contrast, Page::find(3) behaves differently. This method attempts to retrieve a single record by its primary key. If found, it returns a standard Illuminate\Database\Eloquent\Model instance. If not found, it typically returns null. Because this second approach returns an actual model object, the Blade engine can successfully resolve $about->title. The discrepancy becomes obvious when using dd(): the first case outputs the collection's internal array representation (often showing the data nested inside), while the second displays the raw attributes of the model.

To resolve this without switching to find(), you must explicitly tell Laravel to unwrap the result if it contains exactly one item. You can achieve this by calling first() on the collection returned by your query:

public function index()
{
    // Returns a single Model instance or null
    $about = Page::where('page', 'about-me')->get()->first();

    return view('about', compact('about'));
}

Alternatively, if you are certain that exactly one record exists and want to avoid the overhead of fetching multiple records (even though get() might only fetch one), using first() on the query builder itself is a common pattern:

public function index()
{
    // Returns a single Model instance or null without executing a full "select *" for collections
    $about = Page::where('page', 'about-me')->first();

    return view('about', compact('about'));
}

The get() method is generally reserved for scenarios where you anticipate multiple results. For example, if your database contained pages for "about-me", "contact-us", and "faq", running a where clause without specifying a unique identifier would return all matching rows as a collection. Attempting to access $about->title in that specific case would be correct because $about would indeed be a collection. However, mixing the data retrieval method with the expected object type in the view is where errors occur.

When designing your database schema and controllers, it is crucial to align the query method with the intended usage. If you are building a single-page view like about.blade.php, the controller should deliver a single model instance. Using get() on a single-row query creates a collection that lacks direct property accessors for its contents. By switching to first(), you ensure that $about is treated as a model, allowing Blade to render {{ $about->title }} and {!! $about->content !!} without triggering an exception.

This distinction highlights a key trade-off in Eloquent: performance versus convenience. Using get()->first() executes a query that potentially loads all columns (though often optimized by Laravel) and then iterates the result set to grab the first item. In high-traffic applications, using ->first() directly on the builder is slightly more efficient as it instructs the database to stop fetching rows after finding the first match. Always verify whether your variable holds a collection or a model before attempting to access its attributes in your views.

Our network